Platform
What runs underneath: the conversation runtime and its queue, batch workflows, solvers, short links, template inventory, campaign operations and the capability map.
- Audience selectionalso DataDefines who a communication goes to, owning the entry point, the hard suppressions, and the contract by which an eligible population is handed to the runtime that will act on it.
- Batch workflowsDesigns large-scale batch and extract-transform-load workflows with cost gates, throttling, idempotency and a staged test path.
- Capability mapKnows every internal platform capability — accounts, bootstrap, build, distribution, deployment, reconciliation, persistence, connectivity, translation, product orchestration, rule decisioning and the governed vocabulary — and decides whether a request is served by something already deployed before any infrastructure is written.
- Channel assemblyComposes audience, template and send capabilities into one deterministic end-to-end channel service — the internal data contracts, candidate generation, scoring, allocation, outputs and runtime validation.
- Contact scheduling solverHolds how one deployed scheduling solver actually works — how it prioritises records, selects a contact point, respects capacity, assigns hours, rotates between contact points and labels score tiers — and extends it without inventing a parallel runtime.
- Conversation managementManages the fleet around the runtime: the queue a conversation waits in, the configuration each agent runs from, and the tasks raised for a person when a conversation needs one.
- Conversation runtimeServes the conversation itself: holds the task set, runs the agent whose turn it is, calls the functions an answer triggers, and writes what was said to the loan record.
- Mail campaign operationsOperates the deployed mail-campaign workflow: validating the population for a run, launching it, watching it, and reconciling what came back against what was sent.
- Message assistantAnswers questions about what has been sent to a consumer, and lets a non-technical user propose, revise, or retire a message template through a plain-language review conversation that captures the approved wording.
- Rule editorTurns a plain-language request into a concrete change to phone-interaction rules, runs it against sample records to show exactly which numbers would and would not be called, and packages that before-and-after evidence for the rule owner to approve.
- Short linksBuilds the link-shortening and click-telemetry service behind outbound messages: issuing short tokens, storing the link as a graph record, resolving a token through a graph query, redirecting, and publishing a click fact onto the shared event bus.
- Solver servicesDesigns and scaffolds optimisation services: a distributed layer that prepares data at scale, a pure solver core, and the infrastructure that wires them together.
- Template inventoryBuilds the systems that keep message templates versioned, reviewed and in step with whatever sends them — the repository layout, the metadata contract, discovery of the source tables, and one-time or recurring synchronisation from the operational store into a version-controlled inventory.