company logo

Help center

Go to K3X
All collectionsAI AgentsSteps and the AI Analyzer

Steps and the AI Analyzer

Action steps are plain-English instructions the agent executes in order. The AI Analyzer checks for a reply after each one.

Below the goal on the Agent tab are the Action steps: the ordered, plain-English instructions the agent executes. After every step the AI Analyzer checks whether the company has replied, clicked or booked a meeting, and only continues when there is no response.

What a step looks like

A step is one instruction in plain English, for example:

  • Create deal "Demo Booked" on lead "Acme Inc" in stage "Demo Booked"

  • Send an email introducing yourself and asking for 15 minutes this week

  • Wait 2 days

  • Send an SMS: "Hi {first name}, did my email reach you?"

  • Set the custom field "Fit Score" based on industry and employee count

  • Move the deal to "Went Cold" and leave a note summarizing the attempts

  • Send a webhook to https://hook.example.com/k3x with the company name, website and deal stage

You will see the word lead in some generated steps. That is the internal name for a company; it means the same record you see in the Companies tab.

Adding and editing steps

  1. Open the agent and stay on the Agent tab.

  2. Click + Add step at the bottom of the Action list.

  3. Type the instruction. One action per step. If a sentence has "and then" in it, split it.

  4. Reorder or edit steps until the sequence reads like a checklist you would hand to a new hire.

  5. If the agent is Running, your changes apply to new runs. Runs already in progress finish on the version they started with.

The AI Analyzer

The note on the Agent tab says it plainly: "AI Analyzer runs after every step: it watches each company for a reply, click, or booked meeting, and only continues the sequence when there's no response." In practice:

  • After an email step, the agent waits the time you specified. If a reply arrives, a link is clicked or a meeting is booked in that window, the sequence stops for that company and the run ends.

  • If nothing happens, the next step executes.

  • Replies show up on the record timeline like any other email or SMS, so you see the conversation in one place.

This is why you rarely need to write "if they reply, stop" in each step. Write the stop condition once in the goal and let the Analyzer enforce it. If you want a different reaction to a reply, say so in the goal: "If they reply, move the deal to Demo Booked and notify the owner."

Waits and timing

Waits are steps too. "Wait 2 days", "wait until Monday morning", "wait 3 business days" all work. Put a wait between every outbound touch so the Analyzer has a window to catch a response. A sequence with no waits sends everything at once.

Steps that need something to exist

  • Stage names must match a stage in Pipelines.

  • Custom field names must exist in Settings → Custom Fields for the right object (company, person or deal).

  • Email steps need a connected mailbox; SMS steps need an approved K3X number.

  • Webhook steps need a public HTTPS URL. Deliveries show on the Deliveries tab.

Each step that calls the AI or sends a message spends credits from your pool. Waits do not.

Related

  • Goal, triggers and cadence

  • Fix an agent that does not run

  • Custom fields for companies, people and deals

  • Inside a record: timeline, files, fields, owner, agents and deals

Did this answer your question?
😞
😐
😁