Starko

Starko AI answers customersin their own language.

Starko AI replies on the web widget, email, WhatsApp, Instagram and Slack, from your Knowledge hub. You decide how it talks, where it answers, what it is allowed to do, and when a conversation goes to your team.

v2.starko.one/dashboard/ai-settings
Settings/AI assistant
72%

Behaviour

Who Starko AI says it is, how it talks, and what happens when it can’t help.

About your business

Used to introduce you and personalise every conversation.

Company name

Northwind

What you do

One or two sentences. This is how the assistant describes your business.

Reporting and analytics for growing finance teams.

How it talks

The voice Starko AI uses with your customers.

Tone of voice

Natural & friendly

Reply length

Short for chat-style answers, long for detailed ones.

Standard

Greeting

The first message a customer sees in the widget.

Hi! How can we help?

Channels

Choose where Starko AI answers. On a channel it doesn’t, new messages go straight to your team: the conversation is assigned by your assignment rules and flagged for a reply.

Web widget

Starko AI answers first and hands over when needed.

Email

Starko AI answers first and hands over when needed.

WhatsApp

Starko AI answers first and hands over when needed.

Instagram

Starko AI answers first and hands over when needed.

Slack

Off: conversations go straight to a person.

When Starko AI can’t help

Customers can always ask for a person. Decide what happens next, and when idle chats close.

Hand the conversation to

Your team will take over the conversation

Pass to team

Close idle conversations after

Counted from the customer’s last message.

7 days

Ask customers to rate replies

Customers can rate each AI reply in the widget.

At a glance

AI assistant in short.

Where to set it up
Settings, AI assistant: Behaviour, Translations, Actions, Conversation starters and Installation.
Who can change it
Admins and owners. Every member sees its replies in Conversations.
Reply language
Always the language the customer writes in, whatever the widget language.
Tone of voice
Natural & friendly, Neutral, Matter-of-fact, Professional or Humorous.
Reply length
Short, Standard or Long.
Channels
On for every channel by default. Switch each one off on its own.
Tools
MCP servers from the library, your own MCP servers, and legacy HTTP actions.
Price
Free, like the rest of the support side.
Answers

It answers from your knowledge, or says it cannot.

For every message, Starko AI first looks in your Knowledge hub. If the customer writes in another language than your articles, it translates the key terms and searches again before it gives up. When nothing fits, it does not invent an answer: it says it does not have the details and offers to open a ticket so a teammate can look.
  • Show where answers come from: on, replies cite the article links they used. Off, links and references are stripped before a reply is sent.
  • About your business: the company name and one or two sentences on what you do, used to introduce you in every conversation.
  • Advanced instructions: the system prompt, a Latest instruction that takes precedence for current campaigns or temporary policies, and Training examples, pairs of a customer message and the ideal answer.
  • When a ticket already exists for the issue, follow-up details go onto that ticket instead of a new one.
  • For multi-step requests, it follows your procedures step by step.
  • Ask customers to rate replies: customers can rate each AI reply in the widget.
Channels

Choose where it answers, one channel at a time.

The Channels section lists every live channel with its own switch. On a channel that is on, Starko AI answers first and hands over when needed. Switch a channel off and new messages there skip the AI and go straight to your team: the conversation is analysed for a title, summary and tag, assigned by your assignment rules and marked Needs reply.
  • Channels: Web widget, Email, WhatsApp, Instagram and Slack.
  • All channels are on by default, so nothing changes until someone flips a switch.
  • The channel setting wins: Back to Starko on a conversation in a switched off channel keeps it with your team.
  • The widget greeting still shows on a switched off web widget, since it is fixed text.

Channels

Choose where Starko AI answers. On a channel it doesn’t, new messages go straight to your team: the conversation is assigned by your assignment rules and flagged for a reply.

Web widget

Starko AI answers first and hands over when needed.

Email

Starko AI answers first and hands over when needed.

WhatsApp

Starko AI answers first and hands over when needed.

Instagram

Starko AI answers first and hands over when needed.

Slack

Off: conversations go straight to a person.

Handover

Decide what happens when it cannot help.

Customers can always ask for a person. Hand the conversation to sets what happens next: Pass to team, where your team takes over the conversation, or Open a support ticket, where a ticket is opened for the customer. A second setting closes quiet conversations after 3 hours, 2, 7 or 14 days, counted from the customer's last message, or never.
  • Before passing to the team, Starko AI makes sure the customer's name and email are on record.
  • If the customer mentions a ticket, it checks that ticket's status before opening a new one, to avoid duplicates.
  • A handed over conversation is assigned by your rules and flagged Needs reply in the inbox. A teammate's reply takes it off the AI, and Back to Starko gives it back.
Actions

Give it tools, so it can do things, not only explain them.

The Actions page connects Starko AI to your systems. Install a server from the MCP server library, or add your own custom server with its URL and authentication: none, an API key, a bearer token or OAuth. Each server is public or private. Public tools are available to customers in support chats. Private tools stay internal, for ticket auto-resolve and the AI in your dashboard.
  • Built in, Starko AI can search your knowledge base, open a support ticket, check a ticket's status, save the customer's name and email, and read the customer's context.
  • Older HTTP actions, built with the HTTP request builder, still work under Legacy HTTP actions.
  • On your website, it can also run page actions you register in the widget, such as opening a record or switching a view.
  • With Cal.com connected, it offers open meeting slots as buttons and books the one the customer picks.
  • Connecting servers requires the admin or owner role.
Visual replies

Replies can carry cards and buttons.

A tool can return a product card, a product grid, a set of choices or a ticket card, and the widget draws it inside the reply. Choices become buttons the customer taps instead of typing. When Starko AI opens or checks a ticket, the customer sees a ticket card with its number, title and status.
  • On WhatsApp, choices are sent as native reply buttons or a list.
  • On Instagram, choices become quick replies and products are sent as native cards.
  • Product cards and choices come from the MCP tools you connect on the Actions page. Ticket cards are built in.
Back
Export still does nothing for me.
NNorthwindSorry about that. Which report are you exporting?Monthly revenueTeam activityCustom report
Monthly revenue
NNorthwindThanks. I opened a ticket for the team, and you can follow it here.Ticket created#4f2c91a7Export fails on the monthly revenue reportOpenHighView ticket
Type your message...
Translations

Write the widget once. Visitors read it in their language.

The Translations page holds the widget's own texts: the home page, the navigation and the ticket page. You write them, and the greeting, in your language. When a visitor arrives in another language, the texts are translated once for that language and cached for everyone after.
  • Translate now: add up to five language codes at once to translate them before the first visitor arrives.
  • Editing the greeting or the texts updates the languages that are already translated.
  • Conversation starters, where Starko AI opens the conversation, are covered on Outbound. The install snippet is on the widget page.

FAQAbout AI assistant.

Keep exploring

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.

Start for freeGet a demo