Setup and buying help
Connect WhatsApp and prepare your business
Botployment is the operating platform behind the assistant. Prepare the records your team will use for orders, sales or appointments, then connect the channel.
Before connecting
Create your account, verify your email and complete business onboarding. You need access to channel creation and the stores you will serve, an available connection slot, and permission in Meta to authorize the WhatsApp assets. WhatsApp and Telegram share a pool of two connections per active physical store; the virtual main store adds no capacity. Pending and disabled connections still count.
For catalog orders
In Botployment, add products or import an Excel/CSV file. Map its fields and review validation. Check descriptions, prices and the stock policy for each serving store. An import copies data; it does not keep another inventory system synchronized. Decide who will review orders, collect payment and fulfill them using your Botployment workflow and POS.
For appointments
Create your services in Botployment, review their duration and assign eligible employees to each service. Configure the physical store’s working hours, employee schedule assignments and the resources needed for the service. Check availability in Botployment before offering bookings. Optional Google busy-time checks can reduce available times; they do not replace this setup.
Connect through Channels → Add
Choose WhatsApp, select business-wide scope or the accessible stores, then complete Meta authorization for the intended account and number. Standard Cloud API setup saves a pending connection and then requests a six-digit registration PIN; use Finish registration if you return later. Eligible Business app coexistence uses Meta’s phone-linking flow and skips this registration PIN once verified. Do not delete a phone-app account to work around a failed signup.
Review channel settings
Check the assigned stores, whether the channel is enabled, which customers may receive AI replies, and the human-handling duration. Keep catalog, service and business information current. Give the teammates who will handle exceptions the appropriate chat access.
Test an order from beginning to end
Fictional example: add a 250 g coffee bag at ₡4,500 to the Downtown store. Ask for two bags for pickup. Check that the assistant confirms the store and ₡9,000 total, then confirm the order. Open the saved Botployment order and verify items, quantities and store. Review payment and fulfillment separately. A confirmed test can create a real order.
Test a booking and human handoff
Use a service with configured staff and availability. Ask for a time, check the selected service, store, contact and time before confirming, then inspect the saved appointment. In Chat, open human handling and test the return to AI. For coexistence, also test an actual phone-app reply: taking over in Chat alone does not prove that phone replies pause the assistant. Confirmed bookings create real records; cancel unwanted test bookings through the normal workflow.
If setup fails
Check the saved channel before creating another one. For standard signup, use Resume setup with Meta if authorization was cancelled or the number was missing. For coexistence, select the exact number if Meta reports several candidates. Resolve Meta eligibility, asset permissions or missing message delivery with the administrator, then Refresh the connection. Botployment cannot bypass provider restrictions.