Choose capacity around your enquiry process
A conversation and an AI message are different measures. One visitor may send several messages in a conversation, so allow room for useful follow-up questions. Review both limits rather than choosing a plan from conversation volume alone. Your dashboard shows usage so you can evaluate whether the current allowance fits.
Begin with a small, well-tested installation. Check that your knowledge answers common questions and that your team can respond to captured enquiries. A higher allowance will not solve unclear information or slow follow-up. Move to a larger plan when resource limits prevent a process that already works.
Free access and paid prepaid access
The Free plan evaluates your own business assistant within its published limits. It does not require a payment card to create an account. Paid plans offer additional capacity and plan-dependent workspace features. The figures shown above come from the current active subscription records, not an estimated market price.
Monthly and yearly prices represent different purchased periods. Use the interval toggle to compare them. Do not interpret a yearly amount as a monthly bill. Access activates after payment verification, and renewals are manual. Review the expiry information in your account so your team knows when another payment is needed.
Billing records and important checks
Paid checkout uses Razorpay. Billing details are saved in your account, and paid invoices can be downloaded from billing history. Confirm your business details before purchase and check the verified payment result rather than assuming a browser redirect alone confirms access.
This page does not promise a particular tax treatment, refund entitlement, or payment method beyond the configured checkout. If those details affect your decision, contact Digi Digital Solution before purchase and review the service terms. The India pricing page shows only active INR-denominated plans.
Check plan-dependent capabilities
Multi-business access, team limits, branding, widgets, and approved domains vary by plan. Count the businesses and hostnames you actually need. The bare domain and its www version are separate widget approvals; staging sites may need another entry.
Subscription pricing does not include a native WhatsApp messaging bot, a guaranteed external CRM connector, or a promise that every AI answer will be correct. Use the feature guides to distinguish the website widget, contact links, and developer-managed webhooks. Test essential capabilities before choosing paid access.
A simple capacity worksheet for your team
Write down how many websites need the widget, how many people need workspace access, and the volume of conversations you expect during a normal period. Use your existing enquiry records as a starting point if you have them. If you do not have reliable records, use the Free plan to learn about actual usage rather than assuming the busiest day is typical.
Next, check message depth. A visitor asking one question may need a shorter exchange than someone comparing services and arranging a call. Watch both conversation and AI-message allowances during the trial. Leave room for your own testing and review any quota alerts before planning a large campaign.
Knowledge capacity matters as well. Import relevant pages rather than every URL you can find. Remove duplicated navigation content, expired offers, and policies you no longer use. A smaller reliable knowledge set can make testing easier, although it does not guarantee correct answers. Document changes your team makes so a future administrator understands the sources.
For an agency, separate client businesses according to the permissions and workspace structure supported by the plan. Count widgets and approved domains for each website instead of assuming one script can represent every client. White-label access depends on the current plan limits, and it should not be interpreted as a published reseller contract.
Review value without promising a return
Plan cost is one part of the decision. Your team will still spend time maintaining knowledge, checking unclear replies, and following up on enquiries. Compare that effort with the repetitive work you want to reduce. A chatbot can support a process, but higher usage does not itself prove a financial return.
After testing, review whether the saved leads contain enough context, whether staff can continue the conversation, and whether important questions reach a person. Count confirmed outcomes separately from raw chat activity. If you estimate potential revenue, label assumptions and use your own margin and conversion data rather than a claimed industry benchmark.
Before purchase, confirm the required capability in the dashboard and review the service terms. If the product does not offer the workflow you need, more capacity will not create it. Ask about native integrations or channel automation directly rather than treating a webhook option as a complete external system connection.