Success Agent
The Success Agent is the assistant merchants chat with in the Finqu admin. A partner can build support tools, guided workflows, and admin experiences on top of that chat, without building a chat window from scratch.
What you can build
- Merchant support and onboarding. Answer questions, walk through setup, and suggest a next step from the state of the store.
- Guided workflows. Lead a merchant through a job in plain language.
- A single admin experience. Keep the assistant in the flow of your app so it feels like one place to work.
- White-label support. Use your guidelines and skills so every merchant gets the same kind of help.
Behavior is set with the chat mode, skills, guidelines, and which workers the assistant is allowed to use.
Modes
The chat has a mode control with three choices:
- Discuss. For questions and lookups. A skill can be marked Read-only (Discuss mode).
- Plan. The agent lays out steps before the work is done.
- Execute. The agent carries out work the merchant has allowed. A skill marked Write (Execute mode) switches the chat to Execute.
Use Discuss when the merchant should look something up. Use Plan when the path should be visible first. Use Execute when the assistant should do the work.
Workers
A merchant worker is available in this chat when Allow the Success Agent to use this Worker is checked on that worker. Executor, Planner, and Analyst stay separate workers. Work Hub queues each type on its own, with Analyze, Plan, and Execute.
From a finished analyst task the merchant can choose Create a plan. From a finished planner task, Implement. Continue with Success Agent copies a worker chat into this assistant.
Work Hub can also open this chat so the merchant can draft a playbook. A playbook run starts from the product list, from an automation, or from the Work Hub calendar.
Skills
In the chat, Skills are saved prompts the merchant can pick. Add skill asks for:
- Name
- Prompt
- Description
- Placeholder text
- Mode. Read-only (Discuss mode) or Write (Execute mode)
A partner can ship skills that match a workflow, and a merchant can save a repeated prompt as a skill. The chat can also offer to add a skill that was shared with the store.
With the rest of admin AI
- Use Guidelines for tone and limits. Check This guideline applies to the Success Agent also on the ones this chat should follow.
- Connect tools on the Tools screen so the assistant can call an outside service. The merchant can be asked to approve a tool before it runs.
- Open a playbook from Work Hub when the merchant is drafting one. Product-list runs, automations, and the calendar start a playbook. A worker starts from Work Hub, from an automation, or from a schedule, and from this chat when the worker allows it.
Next steps
- Admin AI & Automation — Workers, playbooks, events, and the Success Agent in Work Hub
- Guidelines — Rules aimed at workers, and at this chat when that box is checked
- Inbound MCP Tools — Servers a merchant connects for this chat and for workers
- Workers — Analyst, Planner, and Executor. This chat can use one when the worker allows it