# Less repeated work. A clearer next step.

Your assistant should fit the way your business works. We help organise the information, agree on its responsibilities and set up a useful first workflow with you.

## Help the first conversation move forward.

Prepare answers for familiar questions and ask for the details your team needs. Start with a focused reception flow, such as service enquiries or product questions.

- Answers based on business information you approve
- Relevant details collected one step at a time
- A clear next step when price, stock or timing needs checking

Scope: Within both plans, for the agreed channel and reception workflow.

## Give your assistant something reliable to work with.

We help turn scattered notes into clear business information: what you offer, how enquiries are handled and what should be left to a person.

- Common questions, services and answer boundaries
- A tone that fits your business
- An agreed process for checking and updating information

Scope: Knowledge preparation is part of reception setup. Material scope and ongoing support are agreed with you.

## Let the next person pick up with context.

Agree on when the assistant should stop, what information should be passed on and which questions are still open. Your team stays responsible for the final decision.

- Clear triggers for questions that need judgement
- A concise summary of the customer’s request
- Quotes, complaints and special arrangements left for team confirmation

Scope: Handover is configured and checked with your reception flow. Backend team collaboration is outside these plans.

## Give your assistant an agreed task.

Nominated people can instruct the bot through WhatsApp within the tasks and permissions set up for your business.

- Up to 2 authorised people on RM399, or 5 on RM699
- Responsibilities and allowed tasks agreed during setup
- Confirmation steps for work that needs your approval

Scope: These are WhatsApp instruction permissions, separate from customer enquiries and backend logins.

## From a useful idea to a reviewed post.

Build a repeatable process for preparing content, checking details and publishing through authorised, tested accounts. Agree on who reviews it before it goes out.

- A clear brief, draft and approval process
- Publishing for authorised, tested accounts; formats confirmed per account
- Images and video are not included by default

Scope: Within RM699 as a per-account trial, subject to account eligibility, permissions and agreed checks. AI image and video generation is quoted separately.

## Bring public responses into a considered workflow.

Decide which comments or reviews need a useful answer, which need private attention and where your team should step in.

- A response tone and escalation rules you approve
- Separate setup for reading, public replies and private messages
- Platform-specific checks before a workflow is handed over

Scope: Within RM699 for eligible accounts and agreed actions. Available actions vary by platform and connection.

## Built around your day-to-day work.

1. **Bring one real workflow.**: Share typical questions, the information you use to answer them and the point where your team normally takes over.
2. **Decide what good looks like.**: We agree on the answers, limits, approval steps and accounts involved before configuring the assistant.
3. **Try it together.**: Check familiar questions, missing information and exceptions on your account. Then hand over the agreed workflow with training and support.

The examples on this site illustrate possible workflows. Your service is confirmed around your business, account permissions and the checks completed before handover.