Convert a request into a job in one click

An inbound enquiry through a contact form usually means someone at the agency retyping the defendant’s name and address out of an email into whatever system actually runs the job — a small, repetitive, error-prone step that happens dozens of times a month.

In Trackr, every submission from your embeddable job-request form lands in a dedicated review queue, not your inbox. Open one and you can accept or decline it. Accepting takes you straight into the job-creation form with everything the requester already gave you — defendant details, description, vehicle information where relevant — already filled in. You’re checking and assigning, not retyping.

Where inbound requests come from

Most inbound job requests arrive through the embeddable job-request form sitting on your agency’s own website — sometimes paired with the quote calculator, sometimes on its own. Whoever’s submitting it is typically a client or referrer who already knows the defendant’s details, the address, and roughly what kind of job it is; they’re just not inside Trackr yet.

The review queue, not the inbox

Every submission lands in a dedicated review queue rather than an email inbox, which means it can’t get buried under unrelated messages or missed because someone was away for a day. Staff work through the queue and either accept or decline each request, keeping a clear line between “someone asked us to do this” and “this is now an active job on our books.”

What accepting a request actually saves

Accepting a request takes staff straight into the job-creation form with the defendant’s details, description, and — where relevant — vehicle information already filled in from what the requester submitted. That’s the retyping this feature is built to remove: no copying a name and address out of a form submission into a separate job record by hand, and no risk of a typo creeping in during that manual transfer.

Declining without losing the trail

Not every inbound request should become a job — some are outside an agency’s coverage area or job type, some are duplicates of a request already actioned. Declining a request keeps it in the record as something that came in and was turned down, rather than deleting it outright, so there’s still a trail if a client or referrer follows up asking what happened to it. Agencies that take regular work from the same handful of clients or referrers benefit from the conversion flow doubly, because a referrer who sends jobs weekly isn’t retyped from scratch each time either — their client login lets them submit straight into the same queue rather than a new email to a new person every time. What could be a recurring administrative chore for a busy referral relationship — chasing details, confirming they’re complete, typing them in — becomes a two-click review on the agency’s side instead: read what came in, accept it.