Set Up Your Company

Complete your company profile, business hours, and service area so the AI can work for you.

Start after you know your operating hours, service area, and the policies that should shape customer conversations. These fields feed the public-facing side of your company and any AI assistant you enable.

1. Company basics

Open Settings → Company and enter your legal or trading name, business phone, email, address, and a short overview. Use the name customers recognize, and keep the phone number or forwarding number that your team can actually answer.

2. Hours and coverage

Set business hours for weekdays, weekends, holidays, or after-hours bookings. Add the neighborhoods, cities, or zones you serve so quotes and availability do not promise work outside your real coverage. If you want the AI to give different answers before or after hours, write that rule in the company notes or AI knowledge.

3. Company overview and house rules

Add a concise company overview that describes how you operate: whether you supply cleaning products, whether pets must be secured, whether parking or building access is needed, and any minimum visit time or cancellation policy. Keep these notes specific enough for the AI to repeat them consistently.

4. Save and verify

Save the form, then open your dashboard profile to review the visible summary. Make a test booking request or ask a teammate to confirm that hours, coverage, and contact details read correctly.

Checklist before going live

• Business name matches what callers see on their phone provider.
• Main phone and email are monitored by someone on your team.
• Service area text matches the map or neighborhood list you use in quotes.
• Holiday and after-hours behavior is stated in company notes.
• Any AI knowledge document includes contact, hours, and policy updates.

Tip: Keep hours and coverage accurate. Outdated settings lead to bad answers and booking requests you cannot fulfill.

Setup examples by business size

For a solo cleaner, one phone number, one home region, and three services will be enough to start. A two-crew company should add the exact city zones each crew covers and a single office number that everyone monitors. A multi-branch operation should keep branch names, addresses, and regional policies separate so callers are routed to the right context.

Write an after-hours rule

Decide what should happen when a call arrives outside business hours. The rule can ask the caller to leave a name, service, and property details, or it can capture a booking request with a message that a human will confirm on the next business day. Write the rule in the same wording you want the AI or form to use so there are no competing instructions.

Monthly verification routine

At least once a month, review the company profile, hours, coverage text, and policy notes together. Update them before a holiday, season change, new coverage area, or price change so callers receive current information. Keep a copy of the final version somewhere an owner can approve before it goes live.

Build the company setup checklist

Before opening Settings, gather the source of truth for each field: the phone number customers should call, the number or target used for forwarding, the email the team monitors, the neighborhoods you serve, the hours you can actually staff, and the policies that affect a booking. Write each answer in one line so the setup does not depend on memory.

Test settings as a customer would

After the profile is saved, submit a test booking request for a standard service in the middle of the day and one for an after-hours request. Check that the visible summary shows the correct phone number, service area, and policy note. A quick test catches wording that is correct in Settings but confusing when a customer sees it.

Pair company settings with AI knowledge

The company profile and AI knowledge should use the same wording for hours, service area, minimums, cancellation, supplies, and pets. When one source changes, update both in the same session. A mismatch is harder to spot after calls are live because the AI may repeat the newer knowledge while the public form still uses an older profile.

Walk through one company setup

Use a realistic example during setup, not a blank test. Imagine a three-bedroom home in the center of your coverage area that books a weekly standard clean on Thursday morning. Confirm that the company name, phone, hours, service area, and policy notes allow that customer to receive a clear answer. Then ask what happens when the same customer calls on Sunday evening or asks about a neighborhood one mile outside the service area. The two examples reveal whether the setup is complete enough to trust.

Keep a setup decision log

Write down the decisions made during setup: why the service area stops at a specific neighborhood, which number is the forwarding target, and which policy wording the team agreed to use. A short log helps the next person who reviews settings understand the intent behind each answer.

Verify after every policy change

When you update hours, coverage, deposits, or cancellation rules, run a customer-side test before publishing the change. Open the company summary, review the new wording, and submit the same booking request used during setup. If the old answer still appears anywhere, update the company notes and AI knowledge in the same session. A policy change is complete only when the public form, AI answer, and team instructions say the same thing.

Use a simple setup checkpoint

Before the next month begins, open the company profile, hours, coverage, and policy notes together and ask whether each field still matches the plan for the coming weeks. If a holiday, a new hiring, or a new route changes the answer, update it before a customer sees stale information. A short checkpoint is easier than finding the error after a bad booking request.

Walk through the simple setup scenarios

Start with three practical checks instead of a long audit. First, confirm a customer in the center of your service area can see your hours, phone number, service list, and policy notes without searching. Second, confirm a caller one mile outside the service area receives a clear no or a travel rule, not a generic answer. Third, confirm an after-hours caller reaches the same next-step rule the team would give in person. These three scenarios cover the most common causes of a bad booking request.

Keep company setup answers in one page

Write a one-page operating summary with the exact phone number customers call, the target used for forwarding, the email the team monitors, the neighborhoods served, the hours staff can cover, and the rules that affect booking. Keep it beside the Company settings. When a field changes, update the summary and the setting in the same session so the next person has one source of truth instead of two competing memories.

Create a setup review calendar

Review company setup before the first Monday of every month and before seasonal events such as spring deep-clean demand, holiday closures, or a new hiring wave. On each review date, check the same four fields: hours, coverage, main phone, and policy notes. If any answer no longer matches the calendar, fix it before customers see it. A recurring review is short but keeps the profile from becoming stale.