Templates

Reusable document templates for common CS workflows. Copy these, fill in the customer-specific details, and you’re off.

Discovery & scoping

TemplateWhen to useFormat
Discovery questionnaireFirst customer meeting — structured questions to understand pain points, volume, systems, requirementsChecklist
Technical assessmentPre-sales technical scoping — integrations, data residency, infrastructureChecklist

Discovery questionnaire (starter)

Use this as a starting point for the discovery call. Adapt based on the customer’s industry.

Business context:

  • What is your core logistics operation? (last-mile, freight, port, warehouse)
  • How many orders/shipments per day?
  • What’s your current CX volume? What % is tracking queries (WISMO)?
  • What channels do your customers use? (phone, WhatsApp, email, chat)

Systems & integrations:

  • What TMS/WMS do you use? (Shipsy, SAP, Oracle, custom)
  • What ERP? CRM?
  • What carrier integrations do you need?
  • What telephony/messaging providers? (existing Twilio, Meta WhatsApp setup?)

Data & security:

  • Where is your data hosted? Any data residency requirements?
  • Do you have SOC 2 / ISO requirements for vendors?
  • Is cloud LLM acceptable, or must everything be on-prem?

Success criteria:

  • What does “success” look like for this deployment?
  • What KPIs will you measure? (automation rate, response time, cost savings)
  • What’s your timeline for going live?

Solution design

TemplateWhen to useFormat
Solution architecture docAfter discovery — maps use cases to agents, tools, integrationsDocument
ROI calculatorBusiness case for stakeholders — cost savings vs deployment costSpreadsheet

ROI calculator framework

MetricHow to calculate
Current cost per interaction(CX team cost / month) ÷ (interactions / month)
Projected automation rateStart with 60-70% for WISMO, 40-50% for complex agents
Annual savings(interactions/year) × (automation rate) × (cost per interaction)
Deployment costPlatform fee + integration effort + configuration
Payback periodDeployment cost ÷ monthly savings

Implementation

TemplateWhen to useFormat
Implementation planProject kickoff — phases, milestones, owners, timelineSpreadsheet/Gantt
Integration specEngineering handoff — API endpoints, auth, data mappingDocument
Eval scenario setPre-UAT — test scenarios by categorySpreadsheet

Eval scenario categories

For every agent, build scenarios across these categories:

  1. Happy path — standard input, expected output (5-10 scenarios)
  2. Edge cases — unusual but valid inputs (5 scenarios)
  3. Adversarial — inputs designed to break the agent (3-5 scenarios)
  4. Timeout — slow/unresponsive tool calls (2 scenarios)
  5. Language switch — multilingual handling (2 scenarios per language)
  6. Escalation — out-of-scope queries (3 scenarios)

See Eval framework for how to run these.

Customer-facing

TemplateWhen to useFormat
Demo playbackPost-demo follow-up — what we showed, next stepsDocument
Business caseExecutive buy-in — ROI, timeline, risk mitigationPresentation
Technical overviewCISO/CTO review — architecture, security, deploymentPresentation

Key decks (ready-to-use)

These aren’t templates but frequently-used starting points:

DeckSlidesUse forLink
Agentic Capabilities — Master75Comprehensive overviewOpen
Agent Platform Capabilities1Whiteboard sessionOpen
AgentFleet overview3Quick introOpen

See Decks library for the full catalogue.

Sources

Changelog

  • 26 May 2026: Full content with discovery, solution design, implementation, and customer-facing templates.