Agent Builder for AI agents

​

Rules

1. Read before you write. Call list_agents first. Use only the ids, tool keys, mailbox ids and text-line ids it returns. Never invent them.
2. Confirm before anything that sends. Ask the user before manage_agent with go_live or check_now on a live agent, update, remove, and before apply_agent_change. These tools are marked destructive.
3. Test mode first. launch always starts in Test mode, which sends nothing. Show the user a preview or practice_run before you suggest going live.
4. Follow the house rules. Every firm keeps standing rules (house_rules, one per line) that every agent must follow. Read them before you design or change an agent; list_agents, get_builder_settings and save_agent_draft all return them. Copy the phrases and wording the user gives you exactly.
5. Save standing instructions as house rules. When the user says “always…” or “never…” about how agents behave, offer to add it with update_builder_settings (add_house_rules) so every future agent follows it too.
6. Fix what Lawtte tells you. When launch_problems isn’t empty, or a tool returns an error, it says what to change in plain words. Fix that and retry, or ask the user.
7. Check a call before placing it. For a call agent, run manage_agent with call_check first, then call_place once the user confirms. Both go through the same checks as place_call: consent, calling hours, Do Not Call and daily limits.
8. No sensitive data. Don’t put Social Security, card or bank numbers, dates of birth, passwords or medical details in any field.

​

Build a new agent

​

Blueprint fields

​

Recipe formats

{
  "kind": "thread_followup",
  "config": {
    "mailbox": "<id from list_agents mailboxes>",
    "sequences": [
      {
        "key": "release",
        "name": "Signed release",
        "trigger": "please sign and return the release",
        "body": ["Hi, following up on the release we sent.", "Could you send it back signed?"],
        "waitBusinessDays": 5
      }
    ],
    "maxFollowups": 3,
    "lookbackDays": 14,
    "cc": ["karina@firm.com"]
  }
}

{
  "kind": "text_followup",
  "config": {
    "line": "<id from list_agents text_lines>",
    "sequences": [
      {
        "key": "ro",
        "name": "Repair order",
        "trigger": "please send your repair order",
        "body": ["Hi, just checking in. Could you text us a photo of your repair order?"],
        "waitBusinessDays": 2
      }
    ],
    "maxFollowups": 2,
    "lookbackDays": 7
  }
}

{
  "kind": "call_agent",
  "config": {
    "objective": "Confirm the adjuster received our demand and when they'll respond",
    "recipientType": "adjuster",
    "collect": ["Claim number", "Expected response date"],
    "voicemail": "leave"
  }
}

​

Change an existing agent

• Propose, then apply. get_agent returns its editable fields. Send only what changes to propose_agent_change as desired. You get back each change with an id, a before and an after. Show them to the user, then call apply_agent_change with the proposal_id (and accept to apply only some). This is the only way to change built-in agents (builtin:…).
• Replace the config. manage_agent with action: "update" and the full new recipe (and an optional name). It’s for recipe: agents only.

​

House rules and settings

​

Phone numbers

• Studio account with no number: get_calling_setup_status, then set_up_calling.
• A new number, or the firm’s name on caller ID: request_phone_number with kind: "new" (optional area_code) or kind: "brand" (with phone), plus caller_id_name: up to 15 letters, numbers and spaces, like OCONNOR LAW. The Lawtte team sets it up by hand, usually within a business day.
• Connecting an inbox needs a Microsoft 365 or Google sign-in in the dashboard: Agents → Settings → Channels → Connect an inbox. Send the user there.

​

manage_agent actions

​

Errors