Skip to content

Support

Support answers Conversations with Customers across email, chat and API, and links each reported bug or request to an Issue.

Support answers every Conversation with a Customer, from email, chat, the API or a shared Channel, in one queue. The Customer Lead answers from the Knowledge base with citations and escalates with a summary when unsure.

Summary

PartThis System
GroupSupport
StatusLive
ShelfFront: offered from a Startup’s first days

You can ask:

  • “Answer my customers within an hour”
  • “Hand this conversation to me”
  • “What are customers asking about most?”
  • “Turn this complaint into a bug”

What you get

PartThis System
StartsOn for every Startup at creation, with nothing to install.
Built fromEmail delivery, AI gateway, Search, Workflows

Nouns it owns

NounDefinition
ConversationA Conversation is a Thread with one or more Contacts that a Worker must answer, such as a support request.

Verbs

Events

States

The lifecycle of a Conversation:

Conversation lifecycle: open, waiting, resolvedopen → waiting: on Conversation.answeredopen → waiting: on Action.askedopen → resolved: on Conversation.closedwaiting → open: on Message.createdwaiting → resolved: on Conversation.closedresolved → open: on Conversation.reopenedopenwaitingresolved
StateMeaningMoves to
open (first)A Contact wrote, and a Worker owes the answer by respondBy.waiting on Conversation.answered; waiting on Action.asked when the Question goes to this Conversation’s Contact; resolved on Conversation.closed
waitingA Worker answered, and the Customer owes the reply.open on Message.created when a Contact’s Message arrives in this Conversation; resolved on Conversation.closed
resolvedResolved, confirmed by the Customer or assumed after 72 hours with no reply.open on Conversation.reopened

Who operates it

PartThis System
AccountableCustomer Lead
TeamCustomer Team
SeatA role agent holds it until a Human is seated.
Autonomysupervised
Also calls its VerbsOnboarding Specialist

Approvals and limits

VerbRuleDetail
Conversation.answerLimit for the Customer Lead500 calls per day
Conversation.answerMandate answer for the Customer LeadAnswers Conversations and sends Messages, each through the Startup’s Guards.

Processes that use it

ProcessHow it uses it
SupportA step calls Conversation.answer
Call routingA step calls Conversation.answer

Rail underneath

None.

Views and dashboards

ViewShowsMetrics
QueueOpen Conversations by priority, with the time each has waited.First response time, Agent resolution rate
The Customer Lead’s viewThe Metrics its accountable Role answers for.Month-3 retention, Net revenue retention, Logo churn, Repeat purchase rate, First responses on time, Resolution time

Access

What each Access level may call here.

Access levelMay call
ownerEvery Verb (10)
adminEvery Verb (10)
memberEvery Verb (10)
viewerRead only (2 of 10)

Import and export

ConnectorMode
SlackImport: edits made in the tool arrive as Changes.
Microsoft TeamsImport: edits made in the tool arrive as Changes.

Fees and pricing

None.

Availability and limits

PartThis System
StatusLive

Compliance notes

Controls it carries:

Example

TypeScript
// A payroll managed service. A Customer asks in a shared Slack channel why a bonus was withheld at 22 percent.
import { $ } from 'startup-builder'

// Answered in the same thread, citing the help article, inside the first-response target.
await $.Conversation.answer({ conversation: 'conv_3Fp9', body: 'Bonuses are supplemental wages, withheld at a flat 22 percent. Source: Bonus withholding.' })

// The Customer says thanks. With no reply in 72 hours, the resolution is `assumed` instead.
await $.Conversation.close({ conversation: 'conv_3Fp9', resolution: 'confirmed' })

// Another Customer asks for a person: a Human gets it where one holds the Role above.
await $.Conversation.escalate({ conversation: 'conv_7Lm2', reason: 'askedForPerson' })