Utility questions to service orders
Tickets tagged leak or high bill create a service order in utility billing for a field check.
Zendesk is a help desk tool some city customer service teams, utility call centers and IT departments use to handle questions by email, web form and phone. Each conversation is a ticket with a requester, status and tags.
SentraBridge reads tickets changed since the last run and creates or updates tickets. Tickets about field problems can go to the system that does the work, and the outcome can come back to the requester. Ticket data passes through without being stored.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Tickets | list, read one | create, update | yes | ID, Subject, Description, Status, Priority, Requester… |
Tickets tagged leak or high bill create a service order in utility billing for a field check.
Tickets about potholes or streetlights become Sentra 311 requests routed to public works.
When the service order closes, the Zendesk ticket gets an update and is set to solved.
AMI leak alarms open a ticket so a representative calls the customer.
Systems cities commonly connect with Zendesk, each with its own connector page.
Yes. Zendesk's Ticketing API reads, creates and updates tickets, signed in with an agent email and API token.
Yes. A scheduled flow reads new tickets with a tag, maps them to a 311 category and address, and creates the request.
No. Tickets are read and written in memory. Run history keeps only counts, timings and ticket IDs.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.