For Support teams
The screen your SaaS tools never shipped
Your process runs across Stripe, Salesforce, Zendesk and Shopify, and none of them has the screen it needs. Describe that screen, and Chamfer builds one app across all of them, with your own approval rules on top.

One screen, several systems
Show the ticket, the charge and the booking together, so nobody makes a decision with three tabs open.
Your rules on their data
Add thresholds, two-person approvals and field masking that the SaaS tool itself doesn't offer.
History stays whole
Actions write back through each tool's API, so its own history is complete, and the Logbook keeps the whole decision.
01 — In production
How Tessaly built a refund desk across Stripe and Zendesk
“We described our refunds queue in one paragraph on Monday. By Thursday, 40 agents were working it behind SSO, and every action was logged.”
Ines Albrecht
Support Operations Lead, Tessaly
Read the story
02 — Example apps
Extensions teams built on tools they already pay for
03 — What it includes
What an extension adds to the tools you have
Cross-tool records
Join a Zendesk ticket to a Stripe charge and a Postgres booking by email, ID or any field they share.
Actions through the API
Refund, update, tag or close through each tool's own API, so its history records the change.
Thresholds they don't have
Hold refunds, discounts or credits above an amount for a second approver before the API call runs.
Scoped credentials
Connect each tool with a restricted key or private app token that reaches only what the app uses.
Links from the source
Open the app from a ticket, deal or order with a link that carries the record's ID.
One Logbook across tools
See every action taken in every connected tool in one log, filtered by person or record.
05 — FAQ
What teams ask about extensions
Does this replace the SaaS tool?
Will changes show up in the original tool?
Can we add approvals the tool doesn't support?
What credentials does Chamfer need?
Can we link to the app from inside the tool?
What if the tool's API changes?
06 — More use cases





