Index/ CSM/ The Quick Solution, Mapped
Customer Success · Amazon Quick

The Quick solution, mapped.

How Amazon Quick turns sources into actions — and the four gaps Quick doesn’t fill. The gaps are the job.

Source (data) Quick platform (decide + sequence) Agent + gate (narrate + gate) Action (write / notify) Gap — you build
sources · what quick ingests the gaps · you build, quick does not SalesforceCRM Totangocustomer success Redshiftanalytics S3raw extracts SharePointdocuments Telemetryproduct usage Connectors40+ managed ingest Index · KGretrieval context Orchestratorsequences steps Q Apps · agentthe body Human gatewrite confirmation Write Salesforceupdate record Jira ticketcreate Slack notifyalert ID reconciliationone account ID Deterministic scoringcode decides Grounding · evalcite a real signal Outcome measurementrevenue, not hours sync sync sync sync sync sync ingest context plan draft approve approve approve
01

Sources — what Quick ingests

Salesforce
The CRM. Both a source (account state) and the write target the agent updates.
Totango
Customer success. The risk signals — adoption, health, touchpoints.
Redshift
The analytics warehouse — historical, queryable, aggregated.
S3
Raw landing zone — extracts and logs before anything is modeled.
SharePoint · Confluence
Documents and knowledge — playbooks, runbooks, the narrative context.
Telemetry
Product usage — the behavioral signal the model reads.
02

Actions — what the agent’s hands do

Write to
Salesforce
Update the record. This is the write-back — the action a draft alone can’t do.
Create
a ticket
Jira, ServiceNow — the 50+ built-in actions. Fires a workflow, not a message.
Notify
a human
Slack alert. The hand-off when something needs judgment.

Gate. Every write passes a human confirmation. Quick’s per-action allow/deny and HITL on write actions is the built-in gate — the platform’s version of “human above the loop.”

03

The gaps — what you build

ID
reconciliation
Six sources, no shared account ID. Quick ingests them but won’t reconcile them. Unsafe to act until it does.
Deterministic
scoring
The risk math. Code decides, not the model — Quick narrates but doesn’t compute the score.
Grounding · eval
Does the draft cite a real signal? Quick cites sources for retrieval, but not that the claim traces to the score.
Outcome
measurement
Did the action move revenue, not hours? Quick tracks nothing about renewal or retention.

Through-line. Quick orchestrates and gates. You supply the scoring and the eval. Risk math is code, the model narrates, the human gates — and the outcome is measured outside the platform.

04

How it wires

sync → ingest
→ context
Six sources feed the connectors, land in the index, become the agent’s retrieval context.
plan → draft
→ approve
The orchestrator sequences, the agent drafts, the human gate holds the write until confirmed.
approve → execute
The gated action fires — write, ticket, or notify — and the gap you build measures the outcome.
05

Sources

Sources
Amazon Quick (rebrand of Q Business, 2026) · AWS “What’s Next” event (Apr 2026)