Support assistant: behaviour, tone and escalation

The support assistant is the Starko that talks to your customers in the widget, by email and in messaging channels. It answers from your Knowledge Hub and follows your procedures. Its settings live under Settings → AI assistant on five pages: Behaviour, Translations, Actions, Starters and Installation.

ai settings behaviour

Behaviour

About your business is how the assistant introduces you: your company name and one or two sentences on what you do. How it talks sets the tone of voice (natural and friendly, formal, concise and so on), the reply length (short for chat, long for detailed answers) and the greeting customers see first. The greeting is pre-translated for the languages you add.

Further down the same page you set who Starko says it is and what happens when it cannot help: whether it hands the conversation to your team, opens a ticket, or asks the customer for more detail first.

Actions

The Actions page connects the assistant to your systems so it can do things, not only answer: look up an order, check a subscription, calculate a quote, create a record. Actions are MCP servers. Pick one from the server library (Vercel, Slack, Apollo and others) or add your own custom server by URL; Starko lists the tools each server exposes.

Each installed server has two switches: the first enables it, the second makes it Public. A private server is only used when your team asks Starko; a public one may also be used by the support assistant when it talks to customers. Keep anything that reads internal data private.

ai settings actions

Procedures

Procedures are step-by-step playbooks for specific kinds of requests, for example a refund, a cancellation or an onboarding. The assistant follows them end to end, asking for the details each step needs and calling actions along the way. They are described in Procedures: build step-by-step playbooks for your AI agent.

Translations, starters and installation

These three pages shape the widget itself and are covered in Customising the widget: texts, starters and installation.

Checking how it is doing

Conversations shows every answer with a Starko replied chip; open a thread to read it.

Knowledge Hub → Topic Gaps lists the questions it could not answer, with how many customers asked.

Reporting → Conversations shows resolution without a person, hand-off rate and sentiment over time.

Tips

Keep "what you do" factual. The assistant quotes it.

Prefer a short reply length for chat channels and a long one for email.

When the assistant gets something wrong, fix the article it answered from rather than the prompt; every channel benefits.

Did this answer your question?