Getting started
SAYLS editorial team
The useful short answer
SAYLS connects the conversation with the work around it: an inbox, customer context, team ownership and configured automation. Start with one enquiry, make the next action clear and add modules when they solve a real gap.
A WhatsApp Business Platform is useful when the next action becomes easier to see. A new customer asks a question, somebody owns the conversation, the team can find the context, and the reply moves the enquiry forward. SAYLS brings those pieces into one workspace around an official WhatsApp platform connection. Start with the inbox and add automation where it removes repeated work. You do not need to turn on every module to build a useful first workflow.
A little preparation
Before you start
Have these ready so the next steps feel simpler.
Tick the items you have ready.
What you'll leave with
- A view of how the core tools fit
- A sensible first automation
- A clearer reason to choose a plan
STEP 1 OF 5
Bring conversations into a shared inbox
Connect the intended WhatsApp number and use the Team Inbox to manage its conversations. Instead of several people guessing who replied from a phone, your staff work with the available workspace access and conversation context. If your plan supports multiple numbers, keep the selected-number context clear when answering or configuring messages.
For example, a retailer may use a sales number for product questions and another number for after-sales support. The practical benefit is clarity about which business channel a customer used. Access, number limits and available capabilities depend on the plan, so choose around your team's actual operating model.
Connect the intended number and keep reply ownership clear.
STEP 2 OF 5
Give contacts structure that staff can use
A chat is easier to act on when the customer record is organised. SAYLS includes contacts, statuses, tags, labels, groups and custom fields. Use them for a small set of meaningful distinctions: New enquiry, Awaiting details or Existing customer. A clear field is more valuable than collecting information your team never uses.
CSV import helps bring authorised contact data into the workspace. Check the sample and field requirements, map values carefully and import a small valid file first. Importing a phone number does not create permission to send marketing. Keep your consent evidence and remove unnecessary personal details from records.
Choose a small set of meaningful contact fields and statuses.
STEP 3 OF 5
Automate repeated steps, then keep handover simple
Saved replies help people answer consistent questions quickly. Message bots and flow tools can collect a choice, present useful information or guide a repeatable enquiry. Template-based messaging supports appropriate outbound use cases under Meta's rules. These tools work best when the business has decided the question, response and next step in advance.
SAYLS also has AI capabilities for supported plans and configured providers. Use them with accurate business information and test the answers. A bot and an AI assistant are different controls; do not assume enabling one configures the other. Keep a person available for unusual requests, complaints and actions requiring judgement.
Test repeated responses and the handover to a person.
STEP 4 OF 5
Connect the website and store when the need is real
Website live chat can bring browser enquiries to a team workflow on supported plans. Commerce modules connect supported store events and customer communication, with Shopify and WooCommerce capabilities present in the audited code. API and webhook access offer another route for a business that has the appropriate technical support.
Choose an integration because it solves a specific gap. A shop might need an order event to trigger the right approved message; a service team might need a website visitor to reach an available agent. Account permissions, integration setup and plan limits still apply. A module existing in the product does not mean every business can skip its external setup.
Add a website, store or API connection for a defined business need.
STEP 5 OF 5
Review outcomes and scale the right resource
After your first workflow is running, review where time is still being lost. Is there an unanswered conversation, missing contact detail or confusing handover? Improve that point before adding more automation. Use the reporting and activity context available for your modules to understand the work, rather than assuming more messages always means better service.
As the business grows, compare the next plan against the resource you need: contacts, staff, numbers, flows or specialist features. The current pricing comparison shows the exact inclusions. The reason to buy SAYLS is a more manageable customer process; it is not a guarantee of revenue, perfect AI answers or a business that never needs human attention.
Review the bottleneck before increasing messages or automation.
Bring the steps together
A clearer way forward.
- 01Organise the enquiry
- 02Make the next step clear
- 03Improve the bottleneck
Go to the source
Official references
Provider screens and rules can change. Use the current official documentation for account-specific requirements.
A little clarity goes a long way
