Starko

Your support playbook,followed step by step.

A procedure is a list of steps Starko AI follows when a customer's request matches it: ask for details, use your tools, wait for a teammate's approval and hand off when it should. You write it like a document, not a flowchart.

v2.starko.one/dashboard/procedures/52e0…
Procedures/Plan refund request
72%

Plan refund request

LiveSaveSet to draft

When to use this procedure

Describe the customer intent that should trigger this procedure, including when it should and shouldn’t fire.

Trigger when the customer asks for their money back for a plan they paid for. Do NOT trigger if: - they only ask about prices, invoices or a downgrade

Steps

The steps the agent follows, top to bottom. Add tool calls, branches, and an end. The agent adapts naturally as it works through them.

1.
ASK THE CUSTOMER· pauses until they reply

Which email is the subscription under, and why do you want the refund?

2.
Use Find subscription

Find the subscription and the date of its last payment.

3.
IF

the last payment was more than 14 days ago

1.
HAND OFF TO HUMAN· ends the procedure

Outside the refund window. Summarize the request for billing.

Add step
OTHERWISE
1.
WAIT FOR APPROVAL

Refund the last payment of this subscription.

IF APPROVED
1.

Use Issue refund for the last payment and share the receipt link.

Add step
IF REJECTED
1.
HAND OFF TO HUMAN· ends the procedure
Add step
Add step
4.
END· closes the procedure

Your refund is on its way. It can take a few days to show on your statement.

Add step
At a glance

Procedures in short.

Where
Settings, under Starko AI, then Procedures. Also reachable from ⌘K search.
Who
Owners and admins create, edit, set live and delete procedures.
Starts on
The customer's intent, matched against When to use this procedure. No keywords.
At a time
One procedure per conversation. It switches only when the intent clearly changes.
Blocks
Step, If / Else, Wait for approval, Use a tool, Ask the customer, Look up content, Hand off to human, End.
Tools
Internal tools, MCP tools and your custom HTTP actions.
States
Draft or Live. A procedure needs at least one step to go live.
Price
Free plan, then paid plans. See pricing.
Steps

Write the steps top to bottom, and branch where the answer depends on something.

A procedure has a name, a When to use box and a list of steps. Add a step from the Add step menu and pick its type. Plain steps are instructions in your words. If / Else takes a condition in plain language, like "the order is older than 30 days", with its own steps under IF and OTHERWISE. Branches nest, and each level numbers from 1.

  • Ask the customer pauses the procedure until they reply. It is the only block that waits for an answer.
  • Look up content searches your knowledge base for the step.
  • Hand off to human ends the procedure and passes the conversation to your team, with an optional note.
  • End closes the procedure, with an optional closing message.
  • The editor warns you inline: a plain step phrased as a question will not pause, a step that says refund or book with no tool attached can only talk about it, an If / Else with both branches empty does nothing.
v2.starko.one/dashboard/procedures/52e0…
Procedures/Plan refund request
72%
3.
IF

the last payment was more than 14 days ago

1.
HAND OFF TO HUMAN· ends the procedure

Outside the refund window. Summarize the request for billing.

Add step
OTHERWISE
1.
WAIT FOR APPROVAL

Refund the last payment of this subscription.

IF APPROVED
1.

Use Issue refund for the last payment and share the receipt link.

Add step
IF REJECTED
1.
HAND OFF TO HUMAN· ends the procedure
Add step
Add step
4.
END· closes the procedure

Your refund is on its way. It can take a few days to show on your statement.

Add step
Triggering

A procedure starts when a customer wants what it is for.

On each customer message, Starko reads the last few messages against the When to use of every live procedure and picks the single best match, or none. Write both sides into When to use: when it should start and when it should not. Simple questions and FAQs do not start a procedure; Starko answers those from your knowledge base as usual.

  • It is conservative on purpose: a weak or unclear match keeps the current state instead of starting or abandoning a flow.
  • Once a procedure is running, it continues unless the customer's intent has clearly moved to another one.
  • A procedure that just finished is not restarted by a follow-up question about the same thing.
  • While a procedure waits for a customer's answer or a teammate's approval, it stays in place.
  • What Starko remembers about a returning customer can break a tie on a short first message, never more.
In the conversation

Starko AI follows the steps in order, and handles real conversations around them.

The steps run in order, every time. Each action step is carried out on its own with only the tools that step uses, so a step cannot wander into another one's job. Branch decisions are recorded, so a procedure that resumes hours or days later picks up exactly where it stopped. Questions are asked in the customer's language and your brand voice.

  • When the customer asks something else mid-flow, Starko answers it from your knowledge base and asks its question again.
  • After three side questions in a row, a stronger model checks whether the customer did answer. If not, a teammate takes over.
  • A ticket opened by a step does not stop the procedure. The steps after it, like telling the customer what happens next, still run.
  • Searching the knowledge base, creating a ticket, handing off and saving client details stay available in every step.
  • On voice calls the procedure runs from the same steps, and approval or tool steps become a hand-off, since nobody can approve while the caller waits.
Approvals

Wait for a teammate's yes before Starko does something that matters.

Wait for approval pauses the procedure with a short prompt, like "Refund the last payment of this subscription". The conversation shows Approval needed with Approve and Reject, and the customer is kept informed while they wait. The decision sends the procedure down IF APPROVED or IF REJECTED, exactly as written, without asking a model to decide again.

  • Anyone on your team who opens the conversation can approve or reject.
  • Each outcome has its own steps, so a rejection can end with a hand-off or a different offer.
  • Approvals sit in the inbox conversation, next to the messages they are about.
v2.starko.one/dashboard/conversations/a07b…
Conversations/Ana Kovač
72%
AK
Ana Kovačana@kovac.studio
Hi, we moved to another tool last week. Can we get a refund for the plan we just renewed?
Starko AI
Sorry to see you go. Which email is the subscription under, and what made you switch?
AK
Ana Kovačana@kovac.studio
ana@kovac.studio. We needed a Gantt view for clients. What happens to our projects if we cancel?
Starko AI
Your projects stay available until the end of the billing period, and you can export them from Settings at any time. Your plan renewed 3 days ago, so it is inside the refund window. I have asked the team to confirm the refund and will let you know here as soon as they do.
Approval needed

Refund the last payment of this subscription.

Approve Reject
Tools

Steps act through your tools, not just words.

Use a tool picks one tool for a step and says what to do with it. You can also type @ in any step to mention a tool inline. The picker groups Internal tools, MCP tools from the servers you connected, and Your custom actions, the HTTP actions you set up in AI settings. Saving collects every tool the steps mention, and the procedure may use exactly those.

  • Internal tools: Search knowledge base, Get article content, Create support ticket, Get client context, Check ticket status, Add details to ticket, Hand off to human and Update client info.
  • A refund, a booking or an order change happens only through a tool you connect. Without one, Starko can only describe it.
  • Tools are stored by id, so renaming an action or a server does not break a procedure.
Setup

Your first procedures are drafted from your website.

When Starko sets up a workspace from your site, it reads your forms, your troubleshooting FAQs and your plans, and drafts up to six procedures: one that collects a form's fields in chat, one that walks through a troubleshooting answer and hands off when it fails, and one that helps a customer choose a plan. They wait on the setup review as drafts.

  • Nothing generated goes live on its own. Toggle a draft on in the review, or open it to edit its steps first.
  • A form needs at least two fields to become a procedure, so a newsletter box does not.
  • Regenerating the drafts replaces the ones you never switched on, so copies do not pile up.

FAQAbout Procedures.

Connect a channel and a repository

Turn the support queue into a build queue.

Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.