Your outbound, receipted.
Bellwrit keeps an outbound task tied to its purpose and authorization, then makes the resulting lifecycle easier to review. Start with a clearly synthetic receipt sample.
Receipt preview
Synthetic events with illustrative signature strings.
HMAC-SHA256 · v1 · illustrativeHMAC-SHA256 · v1 · illustrativeReal signed events are available only inside the protected account workflow.
Start with the artifact
A sample receipt, with its edges labeled.
The sample uses synthetic data, including the example callee number +14155550123. It displays the canonical event envelope—eventKey, eventType, callId, occurredAt, signedAt, and data—along with HMAC-SHA256 v1 signature-shaped strings. The values are illustrative; the signatures are not live and cannot be verified.
The sample page is static. It does not load a receipt token, query a call record, or request the receipt API.
Open the Sample / Demo receiptTry it in your account
Run a lifecycle scenario.
The Call lifecycle scenarios runner at /dashboard/sandbox-call requires sign-in. It records provider-free scenarios locally; it does not place a live telephony call. After a run, open the protected call detail to inspect the recorded canonical payloads and signatures.
Create an account, sign in, and run a scenario yourself to see the protected workflow and its signed event records.
Evidence map
What we claim / how you verify it.
Each statement points to an artifact you can inspect, with the limits stated beside it.
The sample shows the event shape
Review its envelope, timestamps, and illustrative signatures at the Sample / Demo receipt. Its signature strings are fake examples, not signed events.
The protected runner records signed events
Sign in at the Call lifecycle scenarios runner to create a provider-free scenario, then inspect the resulting protected call detail. Those locally signed records are distinct from this synthetic sample.
The public receipt exposes a reviewable projection
The Receipt anatomy walkthrough shows purpose, consent, scope, timeline, outcome, and an integrity marker. That marker is separate from lifecycle event signatures.
The compliance pack is starter material
The Compliance starter pack contains starting points for builders. It is not legal advice or a guarantee of legal or regulatory compliance.