Frequently asked questions

Click Start now, then use Proto to configure CRM for your business. Set up your workflows, import your data and invite your team.

The specification covers teams managing territories, complex offers and recurring customer relationships. It connects lead management and pipeline with campaigns, quotes, contracts, receivables, renewals and commissions. You can plan an initial phase around a defined team and customer journey.

It includes sales-related cases and account context. A complete support operation needs its own agreed scope, service processes and connections. Use the case history to inform the customer relationship without assuming every support channel or service workflow is included.

The model distinguishes one-time, recurring and usage charges. Accepted terms define each cycle, minimum, measurement and proration basis. Usage billing consumes the remaining assessed amount for the period, so a minimum already billed is deducted from the later total rather than charged again. Future uncommitted usage stays outside accepted contract value.

Preparation and actual dispatch check the current canonical recipient preferences. Lead conversion, duplicate merging or reassignment preserves restrictive preferences. A previously prepared campaign message must be re-evaluated or cancelled when those restrictions change before delivery.

Reps see their own earnings; managers and operations users receive only their authorized compensation scope. Sales Ops prepares a statement, an independent Sales Manager reviews it, and AR Clerk independently authorizes the payout request. Confirmed provider settlement establishes payment. Acknowledgement alone does not mark it paid.

Yes. The design keeps general-ledger posting and revenue recognition in the configured accounting system. CRM retains operational invoice, receipt and application evidence with reconciled accounting identities. Agree issue, tax, cash and reconciliation responsibilities before enabling the connection.

Every quote line follows its applicable authority. A rep can release a known standard offer within the configured line limits; commercial exceptions go to an eligible Sales Manager. Technical exceptions go to CPQ Admin. Final contract terms need an independent Sales Manager decision, followed by the required customer acceptance of that exact version.

Yes, through a planned and reconciled migration. Preserve source identities, accepted terms, partial fulfilment, original invoice and payment history, and approved earnings. Historical statuses must not trigger new messages, orders, invoices or payouts. Opening totals and remaining obligations are accepted before new processing begins.

Assistants can prepare follow-ups, summarize accounts, explain exceptions and propose actions within their assigned role. Required human approvals remain with the accountable person. Configure and verify the actual application actions, service identity and connections before enabling an assistant on customer data.

Each accepted term has a stable renewal identity and an explicit prior and successor agreement. Continuing recurring base stays separate from uplift and new charges. An auto-renew path follows already signed notice, cancellation and pricing terms plus the authorized renewal action; it does not invent fresh customer consent or an uplift.

There is no per-user fee. The base account and ordinary manual work in the official interface are free. Machine work, retention beyond included allowances and model usage follow the platform rate card; implementation is priced separately. The pricing page explains credit packs, rates and behavior at a zero balance.