Teams running support in Zendesk who want to know which customers cost the most to serve, or whether the accounts about to renew are the ones raising the most tickets.
Pull Zendesk into RowFold tables you own — filter them, report on them, link them to everything else in the workspace.
And it stays current: importing again updates the same tables, adding new records and updating changed ones, so links from your other tables hold. Keep in sync does that for you hourly or daily.
Automation steps that act on Zendesk when something happens in RowFold:
What it doesn't do: It has no say in what a booking page offers. An import only reads: nothing is written back to Zendesk, a record deleted there stays here, and a sync runs hourly at most rather than the moment something changes. Anything else you have read about Zendesk and RowFold, this page is the authority: it is generated from the connector's own code.
This is the question Zendesk structurally cannot answer, because the other half of it is revenue and Zendesk has never seen any. Two imports and one relation get you there, and the organisation is the join that matters rather than the individual user.
You'll know it worked: Pick your largest account and compare its ticket count here against a Zendesk view filtered to that organisation. If they differ, the usual cause is tickets raised by a user whose organisation was never set.
The step needs a subject, a description and a requester email, all three required, because a ticket without a requester is a ticket nobody can reply to. That constraint is worth designing around rather than working around.
You'll know it worked: Fire it on a test record and check the ticket appears with the right requester, not merely that the run went green. A ticket raised against the wrong email is worse than none, because somebody will reply to it.
Zendesk reports on tickets and only on tickets. Cost to serve against revenue, ticket load against contract size, support volume against which version somebody is running: every one of those needs a second system Zendesk has never heard of.
Import tickets, users and organisations, link them to your accounts and contracts, and the comparison becomes an ordinary report.
A ticket that needs real work leaves the helpdesk and vanishes. It becomes a job, a bug or a site visit somewhere else, and the person who promised the customer usually has no way to see whether it moved.
Link the ticket to the work it caused. Support can then answer without asking, and the work carries the customer's name rather than a ticket number.
Anything that ought to become a ticket but starts elsewhere gets raised by hand or not at all — a failed payment, a missed delivery, a monitoring alert.
An automation raises the ticket at the moment the thing happens, with the detail already filled in and the requester correct.
Zendesk's API token authentication identifies the instance, the agent and the token separately: the subdomain says which Zendesk, the agent email says who the calls are made as, and the token authorises them. The permissions you get are that agent's, so a token from a restricted agent sees a restricted set of tickets, which is worth checking if an import looks short.
No. It imports, and it can raise new tickets, and that is deliberately the whole surface. Editing tickets from a second system is how two tools end up disagreeing about the state of a conversation a customer is still having. Zendesk stays the place support works; this is where the tickets get counted and connected.
It can. Importing again updates the same table, matched on Zendesk's IDs, and Keep in sync does that hourly or daily. For the questions this answers — cost to serve, volume against revenue, which accounts are heaviest — a daily sync is plenty, since those are questions about trends. Nothing here is intended to give an agent a live queue; Zendesk already does that well.
If you are already committed to Zendesk and want the numbers connected to everything else, this. If you are choosing now, RowFold's own ticketing sits in the same workspace as the customer, the order and the job, with no import in between and no second place for the conversation to live. The two are genuinely different choices rather than one being a lesser version.
Tickets raised by a user with no organisation set come across with that field empty, which is accurate. It is also probably the commonest reason a per-account report looks short by a few percent. Zendesk's own views hide the problem because they count tickets rather than accounts, so it is worth checking once when the numbers first look odd.
There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.