Know which Workspace setups are worth a scoping call
Every enquiry captures current setup status, domain ownership, and DNS admin access up front, along with the services they want configured. Attach DNS record exports and a user list so you can see exactly what's ready before the call.
Preview your google workspace setup intake
Explore 6 questions from the Google Workspace Setup template. This interactive preview uses illustrative scoring and sample attachments. Open the full survey to try the complete intake.
What a qualified google workspace setup lead should tell you
Guided configuration of a Google Workspace domain and accounts — covering mail, storage, calendar, admin controls, and video — for a business setting up, migrating, or fixing an existing tenant.
- Current Status Google Workspace
- Already Own Domain Name
- How Many User Accounts
- Services Configured As Part
- Have Administrative Access Manage
- Person Authorized Make Decisions
The questions your team needs answered
Every google workspace setup intake asks these — and why each one matters.
| Question | Why it matters |
|---|---|
| What is the current status of your Google Workspace setup? | This separates migrations and troubleshooting requests from greenfield setups, each of which needs a different scoping approach. |
| Do you already own the domain name you want to use with Workspace? | Domain ownership determines whether registration has to happen before any Workspace configuration can begin. |
| Approximately how many user accounts need to be set up? | User count sizes the engagement so you're not quoting a 5-seat scope for a 100-seat rollout. |
| Which services do you need configured as part of this setup? | The selected services define exactly which components (mail, Drive, security, Meet) need to be scoped in the call. |
| Do you have administrative access to manage the domain's DNS settings? | DNS admin access confirms whether MX and verification records can actually be updated without a third-party bottleneck. |
| Are you the person authorized to make decisions about this organization's technology setup? | Confirming decision-making authority prevents scoping time being spent with someone who can't approve the engagement. |
How Cliont scores google workspace setup leads
Configured answer weights help your team prioritize follow-up. Your team reviews each submission and decides the next step.
Value signals
- Not started yet
- Partially set up
- Migrating from another provider
- Set up but having issues
- Already Own Domain Name: yes
- Have Administrative Access Manage: yes
See an example lead handoff
Illustrative lead details and score show how a submission can reach your team.
Google Workspace Setup 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 google workspace setup workflows
| Cliont capability | Google Workspace Setup application |
|---|---|
| Conditional question logic | Follow-up detail can branch on whether the setup status is 'migrating' versus 'not started,' since a migration needs different scoping questions than a greenfield build. |
| Multi-select service checklist | The services-needed question (Gmail, Drive, Calendar, admin controls, Meet) lets you see exactly which components to scope instead of assuming a full-suite engagement. |
| Weighted lead scoring | Domain ownership and DNS admin access are both weighted heavily, so leads who own their domain and control DNS surface as more scoping-ready than those who don't. |
| Decision-maker flagging | The authorization question routes non-decision-maker inquiries differently so you're not scoping an engagement with someone who can't approve it. |
Example google workspace setup lead scenarios
Illustrative situations explain the intake questions and possible follow-up.
Migrating from another provider
The lead is moving off an existing email platform and already flags domain ownership and DNS access, which the intake surfaces as a high-value, migration-ready signal.
Not started, no domain yet
A team wants Workspace but hasn't registered a domain or arranged DNS access, so the intake still captures interest while flagging the missing prerequisites before you scope.
Live tenant with issues
Workspace is already set up but something's broken — the intake distinguishes this from a fresh build so you can scope a fix instead of a full rollout.
Large rollout, many users
A 21-to-100+ user count combined with multiple services selected (security, Drive, Meet) signals a bigger engagement that needs different scoping than a 5-person setup.
Inquiry from a non-decision-maker
The form is filled out by someone who isn't authorized to approve the technology setup, so the intake flags this before you invest time in a scoping call.
Connect Cliont to your workflow
Connect your CRM
HubSpot, HighLevel, monday.com
Connect your legal software
Lawmatics, MyCase, Clio Manage and Clio Grow
Notify your team
Email, SMS, Slack
Configure other destinations
Google Sheets, configured webhooks, Zapier and API workflows
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 cloud services intake templates
Google Workspace Setup lead-intake FAQs
How does the intake tell a migration apart from a brand-new setup?
The setup-status question separates 'not started,' 'partially set up,' 'migrating from another provider,' and 'set up but having issues' into distinct answers, so migrations and troubleshooting requests never get treated like fresh builds.
What happens if the lead doesn't own the domain yet?
Domain ownership is captured directly and weighted lower than an owned domain, so you can see at a glance whether a domain purchase needs to happen before any Workspace configuration can start.
Why does the intake ask about DNS access specifically?
Administrative DNS access determines whether MX records and verification can actually be updated, so it's scored as a strong readiness signal separate from domain ownership.
How does user count factor into the lead score?
The account-count answer, from 1-to-5 up to 100+, helps you size the engagement before the scoping call rather than discovering the true user base once you're already on the phone.
What if the person filling out the form isn't the decision-maker?
That question is captured separately, so leads without authorization to approve the technology setup are flagged rather than treated the same as an owner-approved request.
Do you handle Microsoft 365 intake the same way?
Microsoft 365 Setup is a separate sibling subservice with its own catalog, but it follows the same pattern of capturing current status, admin access, and user count before routing to your CRM.
Turn google workspace setup visitors into qualified clients
Give every google workspace setup visitor a guided intake instead of a dead contact form — and get a scored, qualified lead before you take the first call.