Getting started

Launch your business on Mawidi: a first-week checklist

A practical first week for owners: confirm the business context, prepare booking information, review channels and test one customer journey at a time.

8 min readReviewed 2026-09-12

Key takeaways

• A saved setting needs a refresh check before it becomes a trusted operating fact.
• A customer-facing booking or permitted channel test is separate evidence from setup completion.
• Keep owner-only decisions, provider activation and paid actions with the authorised person.

Day one: establish the business context

Start in Dashboard, then open Settings and review the business information that your account exposes. The aim is a reliable reference for the customer journey, not a promise that every module is available on every account. Complete required fields, choose the matching sector, review hours and time zone, and save one section at a time.

• Open Dashboard → Settings and note which tabs and controls are available to your role.
• Save a small, confirmed change and refresh before making the next change.
• Record a closure or exception only through the control shown by your account.

Days two and three: prepare a bookable offer

Use Appointments to review service types, duration, displayed price and availability. Then use Your booking link in a signed-out window. A successful save is only one checkpoint; the customer view must show the intended service and an available time. Keep a simple test record with the service name, the time you checked and the result you saw.

• Use one service as a worked example: confirm its duration, price and a time that can be selected publicly.
• Do not complete a real booking while testing unless the business has approved the test.
• If a slot is absent, check hours, closures, duration and existing appointments before changing data.

Days four and five: review reception channels

Open WhatsApp and Voice Agent only when the relevant access and provider setup are available. Follow the setup screen, read the displayed connection state and make one permitted test. For voice, review the call record and outcome. For WhatsApp, confirm the test conversation appears in the intended inbox. A connected setting is useful evidence, but it is not the same as a successful customer-facing test.

• Use an allowed test number and identify the test clearly so staff can recognise it.
• Review the transcript, latest message or issue details before changing credentials.
• Keep provider activation and any paid action with the authorised owner or operator.

End the week with a small operating routine

Use the daily checklist to review appointments, conversations, follow-ups and failed or partial records. Invite only the teammates who need access, choose the least-powerful existing role that supports their work, and ask each teammate to verify the intended tabs. Finish by writing down what was verified and what still requires owner or provider action.

• One confirmed booking view, one permitted channel test and one access check are useful weekly evidence.
• Treat an unavailable tab, missing provider record or unresolved error as a follow-up item.
• Never include credentials or private customer data in the checklist or a support request.

Examples

Example: a service appears in Appointments but not in the signed-out booking page. Check saved availability and the current booking link before creating a second service.
Example: WhatsApp reports a saved setup but the test conversation is absent. Recheck the displayed number and inbox, record the state and use Support before resending.