An enquiry about work already with us
You get told who is dealing with it and that they have your details, in one exchange, instead of sending a second email into the same inbox that has not answered the first one. Nobody quotes you a delivery date that has not been checked.
- Industry
- Translation & interpretation
- Shape
- Get it to the right person
- Plan
- Starter and above
Across Translation & interpretation: EzyConn captures and routes the job. It does not translate or interpret.
The situation it is for
The second-biggest source of messages in an agency after new enquiries, and the one that interrupts project managers all day: 'any news on my translation?'. This one takes the why off the front desk — the person who picks it up already knows whether it is a chase, a deadline change, an amendment, an invoice question or a complaint, and who to reach.
A client who has already sent work in messages again — how is it coming along, the deadline has moved, something needs adding, a question about the invoice, or they are not happy. None of those is a new job and none of them can be answered without opening the file, so the bot works out which of the five it is, says who picks it up, takes a name, a number and an email, and puts a person on it with the reason already established.
Who runs it
Agencies running work in progress for repeat clients — which is every agency with an account list.
It starts when somebody types
- “any update on my translation”
- “where is my translation”
- “i need it sooner”
- “chase my project”
- “question about my invoice”
- “i need to change something in my document”
The conversation
What it asks
4 questions, asked in this order. Every answer is written down for whoever picks the job up.
- 01What you need
“What's it about — how the work is coming along, a deadline that has changed, something that needs changing or adding, the invoice, or something you're not happy with?”
Decides which route the conversation takes and which team is named to the customer. Nothing is booked here, so no appointment length is read.
- How my translation is coming along
- My deadline has changed
- Something needs changing or adding
- A question about the invoice
- I'm not happy with something
- 02Name
“And who should we put this down for?”
The name the appointment or enquiry is recorded under.
- 03Phone
“What's the best number to reach you on?”
The only way to reach the customer if anything changes.
- 04Email
“And the email address the work is under?”
The email address it is recorded against.
Those options are the starting set. The services you configure — and, where a process asks for them, the languages you work in — replace them, and the wording follows.
The rules that run
Checks, not judgement calls. The same answer every time, from your own settings.
- Is this a number that actually dials?
What you need set up
Settings in your own account. Nothing here is guessed on your behalf.
- Your services, their length and their price
How it can end
The complete list. There is no other ending it can reach.
- Handed to a person
- Visitor left
Available, with a limit
The limits
This process runs, and it stops short of something its name suggests. Here is exactly what, in full.
- The team is named, not assigned. Either way the conversation goes to whoever picks it up, with the right team written down in front of them.
- It cannot look the job up, and that is the honest heart of this entry. The process establishes who and why and hands over; it never says where the work has got to.
- It does not ask for a job or quote reference. A reference the bot cannot check is a question that costs the client effort and buys the agency nothing — the email address it does ask for is the one identifier a project manager can actually search their own system on.
- A deadline change is not agreed here. The branch records that the client wants one and gets a person on to it; nothing in EzyConn can tell whether the new date is achievable, and a bot that said 'yes, that's fine' would be committing a translator who has not been asked.
- No price is given, and none can be — including on the invoice branch.
- In the numbers, a successful enquiry is recorded with the same word as a booking that had to be handed to a person — so this process’s success cannot be told from a booking process’s failure in a single figure.
And what is not in the product at all
Not a setting you have missed, and not on a list of things arriving shortly.
- There is no connector to a translation management system, and no CRM connector of any kind. What is captured is read by a person and re-keyed into whatever you run on.
- A process cannot look up an order that already exists.
- A handoff writes down the right team and nothing delivers the conversation to it. It reaches whoever picks it up, with the team named in front of them.
More for translation & interpretation
Built on the same engine and the same settings — get it to the right person is one of 6 shapes the whole catalogue is made from.
- TR-01Available, with a limit
Translation request — capture the job to be quoted
Translation & interpretation
You answer ten short questions instead of filling in a quote form and waiting, you see the language pair read back to you so a typo does not cost you a day, and a person picks it up with everything they need.
- TR-03Available, with a limit
Interpreting assignment — book the session
Translation & interpretation
You leave the chat with a real assignment booked at a real time, for the length that kind of assignment takes — not a form and a wait for somebody to check a diary.
Run this one on your own hours, services and postcodes.
Starter and above. Your settings decide the wording, the durations, the prices and the times it offers — nothing on this page is a template you have to accept as written.