Know which website translation leads are worth a discovery call
Ask how many languages a site needs, how much content is involved, and what platform it runs on — then collect the content export before you spend time scoping the project.
The exact intake your website translation leads complete
This is the real 7-question guided intake for Website Translation — the same flow your customers finish before you ever pick up the phone.
What a qualified website translation lead should tell you
Translation of a website's pages, forms, and embedded graphics into one or more target languages, scoped by how much content exists, what platform the site runs on, and whether the work is a one-time project or an ongoing content relationship.
- Many Languages Website Translated
- Approximate Size Website Content
- Platform Or System Website
- Ongoing Support Future Website
- Person Who Can Approve
- Translated Website Be Ready
- Types Website Content Translation
The questions your team needs answered
Every website translation intake asks these — and why each one matters.
| Question | Why it matters |
|---|---|
| How many languages do you need your website translated into? | The number of target languages is a direct driver of project value, so four-or-more-language requests score well above single-language ones. |
| What is the approximate size of the website content to translate? | Content scope (a few pages versus a full site versus ongoing updates) determines whether the inquiry is a small fixed job or a larger, more valuable engagement. |
| What platform or system does your website use? | Knowing the platform upfront determines whether the work involves a straightforward CMS export or a more involved manual/developer-assisted process. |
| Do you need ongoing support for future website content updates? | A yes on ongoing update support signals a recurring-revenue relationship rather than a one-time job, which weights the lead higher. |
| Are you the person who can approve and finalize the translated content? | Confirming the respondent can approve and finalize content identifies the actual decision-maker and helps avoid scoping deals that stall waiting on someone else's sign-off. |
| When do you need the translated website to be ready? | Segments the lead so you can route, price, and prioritize it correctly. |
| Which types of website content need translation? | Forms or interactive elements selected as content type is treated as a complexity signal, since translating functional UI often requires more technical coordination than static text. |
How Cliont scores website translation leads
Every answer is weighted automatically — no manual review required.
Value signals
- One language
- Two to three languages
- Four or more languages
- Not sure
- Ongoing Support Future Website: yes
- Person Who Can Approve: yes
Urgency signals
- Forms or interactive elements
See the lead your team receives
Website Translation Lead
From first click to qualified lead
Follow prospects and clients through one smooth, guided flow.
They land & meet you
Your video greeting plays instantly — a real face instead of a blank form.
They explain the project
Smart questions adapt to their project and capture the full scope.
They share the details
The scope and any documents come attached, so you can scope before the first call.
You get a ready lead
Scored and qualified — waiting for you to win it.
Built for website translation workflows
| Cliont capability | Website Translation application |
|---|---|
| Weighted lead scoring | Language count, ongoing update needs, and approval authority are weighted so multi-language, recurring, decision-maker leads surface above single-page, one-off inquiries. |
| Free-text field capture | The platform question is captured as open text so your team sees the actual CMS or tech stack (e.g. WordPress, Webflow, custom build) before the first call, not a generic category. |
| CRM routing | Leads with full-website scope and ongoing support requests can be routed to your CRM as recurring-revenue opportunities distinct from one-time page translations. |
| Conditional flagging | Selecting forms or interactive elements as content type flags the lead for extra technical scoping before you commit to a timeline or quote. |
Common website translation lead scenarios
Enterprise site, multiple languages
A prospect needs four or more languages across a full website with ongoing update support — the highest-value combination the intake can flag for immediate follow-up.
Small business, single language
A few pages need translating into one language with no specific deadline — still qualified, but scored lower than multi-language or ongoing-support requests.
Urgent site with interactive forms
The client selects forms or interactive elements as content to translate and needs the site ready as soon as possible, which the intake surfaces as a complexity and urgency signal for faster scoping.
Early-stage inquiry, no approver yet
Someone answers 'not sure' on languages and content size and isn't the person who can approve final content — the intake still captures the lead but flags it as needing a stakeholder before a discovery call is worth scheduling.
Connect Cliont to your workflow
Send leads
HubSpot, HighLevel, Salesforce, JobNimbus
Book projects
Google Calendar, Outlook Calendar, Calendly
Notify your team
Email, SMS, Slack
Automate follow-up
Zapier, Webhooks, API
Simple, transparent pricing
Choose the plan that works for your business.
Professional
Unlimited intake forms and leads for your growing business.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Advanced analytics dashboard
Pay Per Lead
Only pay when you receive a qualified lead.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Charged only for submitted leads
More translation and interpretation intake templates
Website Translation lead-intake FAQs
Does the intake ask what CMS or platform the website is built on?
Yes, it captures the platform as a free-text field so you know upfront whether you're exporting from a CMS, working with static files, or coordinating with a developer before quoting.
How does the intake handle sites with forms or interactive elements?
When a lead selects forms or interactive elements as content needing translation, that's treated as a complexity and urgency signal, since form logic and validation text often require extra technical coordination beyond static copy.
Can the intake tell me if the lead can actually approve the translated content?
Yes, it asks directly whether the person filling out the form is the one who can approve and finalize content, which helps you avoid scoping work for someone who still needs sign-off from elsewhere.
What if a client doesn't know how many languages they need yet?
They can select 'not sure,' and the lead still comes through and gets scored — it just signals that a discovery call should include a scoping conversation rather than a fixed quote.
Does the intake separate one-time projects from ongoing translation work?
Yes, it asks whether the client needs ongoing support for future website content updates, which is a strong indicator of recurring revenue versus a single deliverable.
Will I know if a lead is for a few pages or a full-site translation before I call them?
Yes, content scope (a few pages, full website, or ongoing content updates) is captured directly, so you can tell at a glance whether you're pricing a small project or a larger engagement.
Turn website translation visitors into qualified clients
Give every website translation visitor a guided intake instead of a dead contact form — and get a scored, qualified lead before you take the first call.