Who is it for?
Small merchant operations teams connecting a support request to a responsible person and an auditable workflow. Start by defining the request fields, knowledge source, permitted action, approval owner and final ticket state.
What the product advertises
- The support documentation describes intake, knowledge-based answers, routing, a shared ticket table and follow-up messages
- Documents CRM/helpdesk or HTTP requests inside workflows, with branching based on returned data
- Describes an approval node that can pause a workflow for approval, editing or rejection
Platform fit
General support and operations workflows; native Amazon, Shopify and TikTok Shop connections are not verified. Platform tags can describe a native connection, marketplace data, or exported content. The access and limitation notes below explain what to confirm.
Access and setup
An account, configured knowledge and workflow steps, and authorization for any connected systems. Human approval must be configured for the actions that require it. Confirm the current availability and supported workflows in the official product documentation before choosing a plan.
Pricing notes
The reviewed pricing page lists 1,000 monthly credits on Free. AI steps inside workflows are advertised across plans, while creating custom AI agents requires Professional or above. Monthly and annual billing differ; confirm the selected period, seats and credits before purchase. A credit allowance is not a guaranteed number of resolved tickets.
Official pricing & allowances ↗
Limits to check
- General HTTP connectivity does not establish a supported native store connector, refund integration or permission to act on a merchant account
- For a proposed pilot, use a non-sensitive example request and check routing, an ambiguous answer, rejection, retry behavior and the final saved record. Do not equate an approval-node description with a verified default approval policy
- Confirm which system owns the customer and ticket records, what each connection can read or change, and how duplicate follow-ups are prevented
- Documentation reviewed only. No account, connector, agent or workflow was created; answer accuracy, action execution, security and credit consumption remain untested
How to evaluate it
Use the shared evaluation cases and cost worksheet to compare the same task across tools.
Use one real task and a written set of success criteria. Check output accuracy, source traceability, setup time, and total cost. Review any proposed store action before enabling it. This listing summarizes public information; it does not establish performance in your store.
Sources and commercial relationship
Official product source ↗ · Reviewed 2026-11-17.
Official documentation reviewed following a product submission. Submitter identity is not an independent endorsement. No affiliate link, paid placement or independently measured score is used. There is no paid placement on this listing. Read our editorial approach.
Standard listing: ordinary website buttons use nofollow. No approved link exchange is recorded; commercial links are labeled separately. Listing link policy.
- Support workflow and approval model · Reviewed 2026-11-17. Vendor description of intake, routing, knowledge, approval and follow-up; not independently tested.
- Workflow components and connected actions · Reviewed 2026-11-17. Configured triggers, branching and connected steps; connection coverage must be checked for the intended system.
- Plans and custom-agent eligibility · Reviewed 2026-11-17. Free allowance, plan gates and billing options; no checkout or usage test.
Evidence update history
- 2026-11-17: documented feature, access and source review.