Dealership or small business
Tell us about your team, channels, and the work Polly should handle.
Request a business estimatePricing and deployment
Pricing that fits your deployment.
From one dealership to an OEM network, start with your workflows, expected use, and rollout scope. Get an estimate that makes the applicable charges clear before you commit.
Clear scope. Clear terms.
Start with the work you need done.
Your estimate should reflect the workflows, systems, and rollout you are planning.
- Locations and markets
- Channels, integrations, and expected use
- Branding and operating responsibilities
An estimate for a dealership does not define the terms for an OEM or white-label program.
Request an estimate
Choose your starting point.
Share what you know about your business and planned rollout. Expected volume helps, but you do not need every answer to start.
Dealer group or multiple locations
Include locations, shared systems, and your rollout priorities.
Request a group estimateOEM or network program
Discuss markets, dealer workflows, integrations, and governance requirements.
Discuss OEM deploymentWhite-label partnership
Outline branding, client scope, and the responsibilities you want to agree.
Discuss partner termsWhat counts
Understand what creates a billing unit.
When a generated unit is billed
Polly or AI creates an original prospect or direct lead. A completed sale is not required.
Original AI-created prospect
Polly or AI creates the first prospect record. An early inquiry or named handoff can count before full sales qualification.
Direct AI-created lead
AI creates a lead without an already-billed prospect in the same lifecycle.
Later AI-created lead
An AI-created lead from a previously unbilled manual, imported, or passive-form prospect can be billed once.
Exclusions and repeat activity
A call, message, or update is not automatically another generated unit. Other charges may apply under your agreement.
Wrong numbers, spam, and tests
These events are excluded, including when identified during review.
Duplicates and repeat updates
Updates within the same billed lifecycle do not create another generated-unit charge.
Manual, imported, or passive creation
That creation is not a generated-unit charge. A later AI-created lead can be a billable event.
Already-billed prospect conversion
Converting a billed prospect into a lead does not bill it again. Human takeover alone is not a new charge.
Billing scenarios
One lifecycle. No duplicate generation charge.
These examples explain generated units, not every possible charge in a deployment.
Polly creates a prospect
A caller makes an early inquiry. Polly creates the original prospect record, even if qualification is still incomplete.
One generated unit at the applicable account rate.
The prospect becomes a lead
The team updates that billed prospect, follows up, and converts it into a lead in the same lifecycle.
The conversion does not create a second generated-unit charge.
AI develops an unbilled record
A prospect was entered manually or imported without a generated-unit charge. AI later creates a lead from it.
That new AI-created lead can be billed once.
Budget controls
Keep spend visible before demand increases.
Cost Management gives teams a controlled way to review spend, caps, exclusions, and account terms.
Spend visibility
Review generated-unit spend and forecasts in Cost Management.
Configured caps
Generated-unit caps can use call fallback routing. They do not necessarily cap every agreement charge.
Exclusion rules
Review spam, wrong numbers, tests, and duplicates alongside the billing record.
Applicable terms
Confirm the rate and any other deployment charges in your agreement.
Pricing FAQ
Questions buyers ask before rollout.
How do I get an estimate?
Tell us about your organization, locations or markets, channels, systems, and expected volume if known. We will discuss the scope and provide applicable commercial terms before you commit. You can request an estimate without booking a demo.
What counts as a generated prospect or lead?
A generated unit is an original prospect or direct lead created by Polly or AI. A prospect can be an early inquiry and does not need to be a sales-qualified lead or a completed sale. The applicable account terms determine the rate.
Are calls and messages charged separately?
A call or message is not automatically another generated unit. The unit is the original AI-created prospect or direct lead. Telephony, messaging, or other deployment charges may also apply under your agreement; confirm these in your estimate.
Are repeat contacts or conversions billed again?
Updates and repeat contacts in the same billed lifecycle do not create another generated-unit charge. Converting an already-billed prospect to a lead does not create a second charge. A human takeover alone is not a new billing event.
What records are excluded?
Spam, wrong numbers, tests, and duplicate records are excluded. Manual entries, imports, and passive form submissions are not billed for that creation. If AI later creates a lead from a previously unbilled prospect, that new AI-created lead can be billed once. Excluded events may be identified during review.
Can budgets or caps be applied?
Cost Management shows generated-unit spend and supports configured caps with call fallback routing. These controls do not necessarily cap every charge in an enterprise agreement. Confirm the relevant controls and other charges during scoping.
How are OEM and partner terms agreed?
OEM, network, and white-label deployments are scoped around their markets, workflows, branding, integrations, and operating responsibilities. Commercial terms are agreed for that deployment; a dealer estimate is not a quote for an OEM or partner program.
What if we already have an agreement or an earlier offer?
Existing agreements continue to govern their applicable fees and scope. If you have an earlier offer, share its reference so we can confirm what applies. A change to the website does not itself change your agreed terms.
Next step
Get an estimate for your deployment.
Tell us about your organization, expected use, and rollout requirements. Review the applicable charges and assumptions before you commit.