Answer common questions
Provide information about opening hours, services, location, product details, delivery options, and other topics covered in your approved business knowledge.
See how Shilte AI can automate your enterprise operations.
Our team will review your requirements and reach out within 24 hours to schedule your walk-through.
Want an immediate consultation?
Continue on WhatsAppLearn how WhatsApp can become an AI-assisted customer channel for your business—including Meta Embedded Signup, selecting business assets and phone numbers, testing conversations, handling hand-offs, and monitoring messages after launch.
WhatsApp AI combines a messaging channel with an AI assistant that can respond to customer messages using your business information and the capabilities enabled in your Shilte workspace.
Instead of requiring customers to visit a website, find a contact form, or wait for a staff member to respond to every common question, they can message your business through WhatsApp. The AI assistant can help answer inquiries, guide customers, and support selected workflows when those features are configured and available.
WhatsApp is already a familiar channel for many customers. With a configured AI assistant, it can support everyday customer engagement and help your team organize inquiries.
Provide information about opening hours, services, location, product details, delivery options, and other topics covered in your approved business knowledge.
Help collect relevant details from prospects so staff can follow up. Avoid requesting unnecessary personal information.
Where catalog or commerce capabilities are configured, help customers explore products and ask questions before purchase.
Guide customers toward the next step, such as requesting a quote, asking for a booking, or contacting the team, when those workflows are available.
Offer automated responses when your team is unavailable, while making it clear when a human response may take longer.
Handle recurring informational questions to give staff more time for cases that need judgment or personal attention.
Complete these checks before starting. Preparation reduces setup errors and helps you test the connection more confidently.
Use this preparation guide before launching Meta Embedded Signup. It brings together the business, account, phone-number, billing and technical checks that can help make onboarding smoother.
Have access to the Meta Business Portfolio associated with your business. You may be asked to select an existing portfolio or create one during onboarding.
Prepare your business name and any other requested details. Use accurate information that matches your business records.
Choose the number you intend to connect and confirm you are authorised to use it for your business WhatsApp setup.
Be able to receive and complete any verification Meta requests for the selected phone number.
Prepare the name customers should recognise. Meta reviews display names against its business and messaging policies.
Make sure you can manage the relevant Meta Business Portfolio and WhatsApp Business Account, or have an authorised administrator assist you.
Review Meta's WhatsApp Business Platform billing requirements. Requirements and available payment methods can depend on the account and country.
Use a reliable connection and keep your browser open while completing the authorization and setup process.
WhatsApp Business Platform messaging may involve charges set by Meta. These charges are separate from any Shilte AI service fees. Review Meta's current pricing and billing requirements before proceeding. Applicable requirements may vary by country, account type and messaging category.
Review WhatsApp Platform pricing ↗Tick each item as you prepare. Your progress is calculated in this page and is not submitted to Shilte or Meta.
0% complete — prepare each item before you begin.
You use Meta's onboarding experience to select and authorize the relevant WhatsApp Business assets.
After authorization, Shilte's integration processes the connection through its backend and associates the relevant connection with the correct business workspace.
Once setup is complete and the account is eligible, the connected number can be used by the WhatsApp messaging features supported in your Shilte workspace.
Meta Embedded Signup is the guided onboarding experience that lets an eligible business authorize WhatsApp Business assets for a platform such as Shilte, without manually sharing its Meta password with Shilte.
When this flow is available in your Shilte workspace, use the in-app Connect WhatsApp or equivalent button to begin. The authorization window is provided by Meta. The exact screens and available choices can vary based on the business's existing Meta setup, permissions, account eligibility, and the current Meta interface.
Open the WhatsApp integration area for the correct business. Choose the connect/onboard option that launches Meta Embedded Signup, if provided in the current interface.
In the Meta-hosted window, sign in to the account that has appropriate administrative access to the business assets you intend to connect. Complete any requested security checks.
Choose the business portfolio you intend to use, or follow Meta's prompts to create one if that option is offered and you are authorized to do so. Use the business's correct legal and contact details.
Choose the eligible WhatsApp Business Account, or create/setup one through the guided steps when available. Review the account name and business details carefully.
Follow the on-screen instructions to use an eligible phone number or add a new one. Meta may require number verification. Existing-number eligibility and migration/coexistence options depend on Meta's current rules and your account configuration.
Read the requested permissions and confirm that the correct business assets are selected. Grant only the authorization needed to connect the intended assets to Shilte.
Complete any remaining Meta steps, close or return from the authorization window, and wait for Shilte to report the connection result. A completed Meta authorization screen alone is not proof that Shilte has finished configuring the channel.
Check the connected account/number shown in your workspace, confirm it belongs to the correct business, and send a controlled test message before launch.
startWhatsAppOnboarding() integration. This tutorial page cannot independently create a Meta authorization session; the function and backend configuration must be present in the live Shilte application.Confirm that Shilte has received the authorization and completed its own channel setup. Check the business-to-number mapping, test inbound and outbound messaging where supported, review the AI's business knowledge, and establish a human follow-up process. If the flow fails or the connection does not appear, use the troubleshooting section rather than repeatedly starting new onboarding sessions.
WhatsApp Business messaging typically involves an approved business account and phone-number configuration, a messaging connection, and a routing layer that identifies which Shilte business workspace should handle an incoming message. Exact setup steps depend on the connection method offered in your Shilte account.
Controls the business messaging account, phone number, and applicable permissions or verification.
Holds your business context, AI configuration, and enabled capabilities that shape how incoming conversations are handled.
Helps associate incoming messages with the correct business workspace and connected number.
Delivers AI responses or routes a conversation to the configured support process when needed.
For the actual connection, use the integration options and instructions shown inside your Shilte workspace. This guide does not assume that every account uses the same onboarding flow.
Make sure your assistant has a useful foundation. A WhatsApp channel can deliver messages, but it cannot compensate for missing, outdated, or contradictory business information.
Decide what the AI should answer, what it may collect, what it should not promise, and when it should direct a customer to a staff member. Include instructions to acknowledge uncertainty instead of inventing facts.
For detailed document-upload and knowledge preparation guidance, visit AI Knowledge Hub.
Use the current instructions in your Shilte account as the authoritative guide for the available integration flow. The following sequence is a general preparation and verification workflow.
Sign in to your business account. Confirm that you are working in the correct business workspace, not another tenant or test account.
Open the integrations or channel configuration area and select WhatsApp if it is available to your account. Review the setup information displayed.
Complete the authorized account connection, number selection, permission approval, or credential entry steps shown. Do not share login passwords or verification codes with anyone.
Double-check the number, business identity, and workspace assignment before saving or completing setup.
Look for a connection or configuration status in the dashboard. A saved configuration is not the same as a successful live-message test.
Send test messages from a separate phone or permitted test account. Confirm that the correct workspace receives the message and the response behaves as expected.
For multi-business platforms, incoming messages must be associated with the correct business context. Verify that the phone number connected to WhatsApp is mapped to the intended Shilte business account.
| Check | What to verify |
|---|---|
| Phone number | The connected number is the one you intend customers to message. |
| Business assignment | The number is associated with the correct business/workspace. |
| AI context | Test replies use the correct business name, knowledge, services, and policies. |
| Test isolation | Test messages do not accidentally route to another business or customer context. |
| Ownership/access | Only authorized administrators manage the connection and related settings. |
Do not treat a phone number or workspace identifier in a link, configuration screen, or message as proof of authorization. Access controls must be enforced by the system, not by relying on a visible identifier alone.
Testing helps you identify incomplete knowledge, routing problems, and unsafe responses. Use real-world phrasing rather than only the exact wording of your FAQs.
“Hi, what services do you offer?”
“Are you open on Sunday? What time do you close?”
“How much does this cost? Are there any extra charges?”
“Can you help me with something?”
Ask about a product, policy, or service not covered in your knowledge and verify the AI acknowledges uncertainty.
“I need to speak to a real person.”
AI is useful for routine conversations, but some customers need a person. Define how your team will take over and how customers will know what to expect.
Messaging integrations handle customer information. Protect your business and your customers by limiting access, minimizing data collection, and following WhatsApp's applicable policies and local privacy requirements.
For security or privacy questions, review your organization’s requirements and the current official guidance from Meta/WhatsApp and relevant authorities.
Use this checklist as a final review before promoting the number or inviting customers to message it.
After launch, regularly review conversations and the questions customers actually ask. These can reveal gaps in business knowledge, confusing instructions, or opportunities to improve customer service.
Identify repeated questions that the AI cannot answer and add reliable information where appropriate.
Review whether answers are accurate, helpful, on-brand, and appropriately cautious.
Understand which topics need staff intervention and whether the support team is following up.
Refresh pricing, inventory information, operating hours, service changes, and policies when they change.
Use insights to improve the service—not to assume that more automation is always better. Keep a human path for requests that need judgment or verification.
| Issue | Possible checks |
|---|---|
| Messages are not reaching Shilte | Check connection state, number/account selection, provider-side setup, permissions, and whether the number is configured as expected. |
| Wrong business context in replies | Verify phone-number mapping and the selected workspace. Test with a known number and known business questions. |
| AI replies are inaccurate | Review missing or conflicting knowledge, prompt/policy configuration, and the question's ambiguity. Correct the source and retest. |
| AI does not know an answer | Provide approved information if available; otherwise make sure the AI admits uncertainty and offers a staff follow-up. |
| Customer expects an action that did not happen | Verify whether that action is actually enabled and whether a confirmed result exists. Avoid treating a message as proof that an action completed. |
| Human follow-up is delayed | Check staffing, notifications, and the hand-off procedure. Adjust the response to reflect actual support availability. |
| Connection stops working | Check provider account status, integration alerts, recent configuration changes, and official provider guidance; contact support if needed. |
Keep a short record of the issue, approximate time, relevant non-sensitive error message, and steps already attempted when contacting support. Do not include customer secrets or authentication codes.
No. It can help with routine inquiries, but staff remain important for complex cases, exceptions, sensitive conversations, approvals, and customer relationships.
No. The channel delivers conversations; answer quality depends on the business knowledge, configuration, capabilities, and testing. Monitor responses and improve the knowledge sources over time.
Eligibility and migration or coexistence options depend on your current setup and the provider's rules. Check the official onboarding instructions before making changes to a number that customers already use.
Multi-number availability and routing depend on the features enabled in your Shilte account. Confirm the current options in your workspace and verify each number's business mapping separately.
That depends on which commerce and payment features are implemented, connected, and enabled for your business. Do not assume a conversation automatically creates a valid order or confirms a payment; verify the system's confirmed transaction status.
It should acknowledge that it does not have enough information and direct the customer to the appropriate human support process rather than guessing.
Review real conversations, identify recurring knowledge gaps, update accurate source information, adjust guidance, and retest important scenarios.
Visit the Shilte website or sign in to your workspace for account-specific settings and feature availability.
Use this space for a screen-recorded walkthrough showing the actual WhatsApp integration options available in Shilte. Record the steps from your current dashboard rather than showing an outdated or hypothetical flow.
Replace this placeholder with your embedded tutorial video when ready.
Build on this tutorial by learning how to prepare knowledge, manage leads, configure business workflows, and deploy your website assistant.
Prepare documents and reliable business information for your AI.
Explore the tutorial →Learn how customer conversations can support lead-management workflows.
Explore the tutorial →