Interpretation and translation enquiries, captured properly.We route the job. We do not translate it.

EzyConn captures and routes the job. It does not translate or interpret.

• EzyConn does not translate and does not interpret

  It captures the job and gets it to a person. The linguistic work is done by your linguists, and nothing on this page should be read as the software doing any part of it.

• No price, ever

  There is no word count, no per-word or per-hour rate, and no quote record anywhere in the product. A figure typed into a chat window would be invented, so the process collects what a person needs in order to quote and says exactly that. Do not reword it so that it implies otherwise.

• The material cannot be attached

  No step invites a file, and a document uploaded mid-conversation never reaches the process — the conversation simply sits on the question it last asked. The job is described in words instead, which is why the volume question offers ranges rather than a word count.

• It cannot look a job up

  There is no project or job record for a translation in the product, so no step can read a reference, a status or a delivery date. The chase process establishes who is asking and why, and hands over; it never says where the work has got to. It does not even ask for a job reference, because a reference it cannot check costs the client effort and buys the agency nothing.

• A deadline change is not agreed, and a complaint is not a case

  The deadline branch records that the client wants one and gets a person on to it — nothing here can tell whether the new date is achievable, and a yes would commit a translator nobody has asked. The complaint branch becomes an ordinary handed-over conversation: there is no complaint or ticket record, nothing ages it, and nothing reports on it.

• Nothing checks that you cover the pair

  No rule in the product reads a language list. A pair you do not staff is captured exactly as the client typed it — and on the interpreting process, booked — for a person to unpick. A language you have configured is normalised to your own spelling; anything else is recorded verbatim.

• The interpreting booking reserves your diary, not an interpreter

  This is the sharp edge of the vertical. The assignment is written against the business, not against a linguist — there is no skill or resource model — so two assignments in different languages at the same hour are indistinguishable to it. An agency whose real constraint is interpreter availability rather than diary space should capture the job and have a person confirm the linguist before anything is booked.

• The pair is not on the assignment itself

  It is in the conversation and on the record of the run, permanently — but a coordinator reading the diary alone sees a two-hour in-person assignment without seeing which language it is in.

• No translation-management or customer-record connector

  Nothing connects to a translation-management system or a CRM — a captured request is read by a person and re-keyed into whatever you actually run on. Everything that leaves does so through Zapier or your own signed webhook.

• Certification is recorded, not ruled on

  The process asks who is asking for the certification and writes it down, because a wrong "yes, that will be accepted" can cost somebody a visa appointment. It never says whether a certified document will be accepted by a particular authority.

• The venue is captured, not checked

  There is no coverage check on interpreting — a phone or video assignment has no address at all — so an agency that must refuse out-of-area in-person work does not get that here.

• No calendar sync, of any kind

  Not Google Calendar, not Outlook, not Calendly. Availability is worked out only from appointments EzyConn made itself, so a time you blocked out in your own calendar is still offered to a customer.

• No system connectors

  There is no customer-record, scheduling-system, order or field-service connector in the product. Everything that leaves does so through Zapier or a signed webhook to your own endpoint.

• The confirmation is an email, never a text message

  No process sends SMS. The confirmation email is best-effort: if the queue behind it is down, a real appointment can be made without the email arriving. A cancellation sends the customer nothing at all — the chat window is their only confirmation.

• Nothing is paid for in the conversation

  There is no payment step anywhere in a process. No deposit, no card, no voucher, no balance.

• A service area is a list of postcodes, not a radius

  You give a list of postcodes or a prefix to match on, for one country. A radius is refused outright, and so is covering everywhere.