Overview
Open the staff assistant from a Gorgias ticket with its ID already selected. The redirection link uses the documented ticket template, and the staff backend loads an authorized ticket snapshot.
Your team hosts the staff interface and case-access checks; Voiceflow runs the published read-only assistant. Tasks run only on a staff action. Automatic selection loads a snapshot, not a live transcript or a customer-send action.
Prepare the staff deployment
Collect the assistant, verified identity and platform configuration once.
Download the starter bundle. Keep support-platforms, contact-center-assist and amazon-connect as sibling directories. Shared agent-assist setup owns the host/session contracts; build the staff assistant before installing the platform entry.
Install the staff entry
Generate the platform files, connect authorized data and activate the pilot surface.
Build the platform files
From the extracted archive root, use your HTTPS staff origin without a path:
Serve the generated panel.html, panel.css and panel.bundle.mjs together at https://staff.example/support-platforms/gorgias/panel.html. The command also writes SETUP.md and the applicable platform artifacts. Keep credentials on the server. It refuses an existing output directory; append a new directory after the origin when rebuilding. Configure no-store, approved iframe ancestors and embedded SSO.
Connect the authorized case reader
Use the supplied read adapter rather than writing the provider fetch/allowlist yourself:
Set ASSIST_PROVIDER_ORIGIN to the fixed provider origin, such as https://your-account.gorgias.com. authorizeRecord(staff, id, {platform, signal}) must return true only after checking staff membership, tenant and record/field access for that configured instance. The reader checks this before retrieving credentials or reading the provider.
authorizationForStaff(staff, {platform, signal}) returns the server-held Basic … authorization value from approved server credential storage for that approved account. A shared integration credential does not establish a staff member’s entitlement. Review the reader’s fixed field allowlist before use; token consent, storage, expiry and rotation remain in your identity service.
Mount the handler at both same-origin POST paths, /api/agent-assist and /api/agent-assist/context. Apply the host’s CSRF policy to both, a 32 KiB body limit, staff rate/concurrency limits and bounded identity/provider reads. Honor the supplied cancellation signal. The context route starts no Voiceflow session; every later task reauthorizes and reloads the record.
Activate the platform surface
Open a saved ticket, edit the sidebar widgets and add a standalone widget or use an approved existing widget. Choose Add Redirection Link, set the title to Voiceflow agent assist, and paste the generated launch template from SETUP.md:
Keep the ticket.id template; substitute only the HTTPS staff origin. Save the link and widget configuration. Use a redirection link rather than a custom action button that performs a provider mutation.
Load context and choose a task
Open the installed entry for an allowed sandbox record; confirm the selected ID without typing. Wait for Case context ready and inspect Approved case context. Denial keeps tasks disabled. Opening a record or loading context does not ask the model.
Choose Find policy, Draft reply, Suggest next step or Summarize. The question box is optional for these four actions; use it to focus the result. Ask assistant requires a question. Configure the assistant to return customer wording only for Draft reply and staff evidence/missing facts for the other tasks. Review model output before using it.
Configure case context
Treat workspace IDs as selection hints and keep approved data on the server.
Gorgias expands {{ticket.id}} for the current ticket. The browser treats it as a lookup hint; the server checks staff account and record access before reading. This external tab is pinned to the launched ticket and cannot follow later Gorgias tab changes. Reopen the link for the next ticket. The default reader includes ticket metadata only; add a separately authorized issue excerpt when guidance needs more detail.
Use Copy suggestion only after the complete result arrives, then review/edit it in the normal support workspace. This supplied surface has no verified draft-composer insertion action. A provider endpoint that sends a message or saves a note is not used as a substitute.
The host must reset/unload on logout and account changes. Browser abort stops consumption; it does not prove remote execution stopped or transcripts were deleted. Set expiry and retention with the owning teams. A snapshot above the starter’s 16,000-code-unit limit is rejected; narrow the approved fields instead of silently dropping conversation coverage.
Test the staff workflow
Check tasks, record changes, denial and the exact human delivery action.
Check the selected record and all four tasks
Use a sandbox case with an unopened item delivered 12 days ago and an approved 30-day policy. Confirm the visible record ID and approved snapshot. Run every task with an empty question, then add a focus. Verify policy conditions, missing facts and source references. Summaries must state gaps when the snapshot is metadata or a limited excerpt rather than a complete interaction.
Prove record isolation and access denial
Launch a second record and confirm its ID/context replace the first in that new launch. Existing companion tabs remain pinned to their original record; finish/close them deliberately. For manual selection, edit the ID mid-response and prove tasks stay disabled until the next context load succeeds. Use a second staff account for a denied record: no snapshot/answer may appear and no model request may start. Test logout, account switch and session expiry.
Review delivery and recover from failure
Copy one completed suggestion and review it in the normal composer. No provider send, saved note, refund or call-control request may occur. Verify a partial stream never enables Copy suggestion. Interrupt the stream and deny the provider read; the prior/partial result must clear. Restore the service and retry manually while keeping the normal support workspace usable.
The entry or context does not load
Check platform assignment, direct origins and staff/provider access.
Verify the generated URL/artifacts, platform assignment and embedded sign-in. For parent messaging, verify both the direct source window and configured HTTPS origin; never use a wildcard. A 401 requires sign-in; 403 requires CSRF/tenant/record checks; 413 needs a narrower approved snapshot. Inspect redacted server diagnostics for provider/runtime failure. Reopen/reload after recovery without exposing the staff service publicly.
The result belongs to an old record
Check whether this surface follows selection or opens a pinned companion.
Compare the visible ID with the workspace. For a pinned launch, open a new launcher for the current record; a separate tab cannot follow the original workspace. For SDK/property binding, repeat the switch during the pending response and check the direct parent/SDK events and generation guard. Do not rely on a network abort alone. Discard an uncertain result before continuing.
Release and maintain assistance
Record the accepted app, permissions and rollback before expanding access.
Release to the pilot staff
Record the staff-host build, provider field allowlist/mapping, platform configuration and Voiceflow Environment/release. Repeat allowed/denied cases through the actual installed entry with a fresh staff session. Assign owners for policy freshness, identity/token lifecycle, SDK/app updates and incidents; rerun quality evaluation after changes.
Restore the reviewed deployment
Remove the redirection link or pilot widget in sidebar edit mode and save; no ticket or customer routing changes are required. Restore the recorded staff-host build and reviewed Voiceflow release, then repeat a fresh-session check.
Local review uses the starter’s labelled fictional fixtures; no SDK fixture or successful bundle proves provider installation, SSO, account permissions or real-model quality. Complete sandbox acceptance for this exact surface before release. For business-system tools, Import help articles and Human agent hand-off, keep the canonical Integration manuals.