> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avidra.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Hours

> Define when your business is open and how Avidra should behave after hours.

Business Hours tells Avidra when your business is open and what should happen outside those hours. This affects message content and how the dashboard reports workspace state.

## What you configure

| Setting                | Purpose                                               |
| ---------------------- | ----------------------------------------------------- |
| Business hours enabled | Toggle hours-aware behavior on or off                 |
| Weekly schedule        | Define open hours for each day of the week            |
| Timezone               | Ensures hours are evaluated in the correct local time |
| After-hours SMS copy   | Custom message sent to callers outside business hours |

## Why it matters

Business hours are not just cosmetic — they affect real behavior:

* Whether Avidra treats the workspace as open or after-hours
* What message content is sent to callers outside normal hours
* How the dashboard reports the current workspace state
* Whether the AI adjusts its promises about callback timing

## After-hours messaging

When a caller texts during business hours, Avidra responds with your standard recovery message. Outside business hours, Avidra can send a different message that sets appropriate expectations.

### Examples

**Good after-hours message:**

> "Thanks for reaching out. We're closed right now but open at 8am tomorrow. We'll follow up first thing in the morning — what do you need help with?"

**Bad after-hours message:**

> "We are currently closed. Please try again later."

The good message tells the caller when you open, commits to follow-up, and still asks for details so your team has context in the morning.

<Warning>
  Setting correct hours in the wrong timezone is a common mistake. Double-check your timezone setting first.
</Warning>

## Setting up your schedule

<Steps>
  <Step title="Set your timezone">
    Select the timezone that matches your business's physical location. All hours are evaluated against this timezone.
  </Step>

  <Step title="Define your weekly hours">
    Set open and close times for each day of the week. Leave a day blank if you are closed.
  </Step>

  <Step title="Write your after-hours message">
    Customize the SMS that callers receive when they reach out outside business hours. Be specific about when they can expect a callback.
  </Step>

  <Step title="Enable hours-aware behavior">
    Toggle on the business hours feature so Avidra uses this schedule.
  </Step>
</Steps>

## Best practices

<Tip>
  Your after-hours message sets expectations. Something like "We'll call you back first thing tomorrow morning" works better than a generic "We're closed."
</Tip>

* Set the correct timezone before configuring hours
* Review holiday or seasonal schedules manually when needed — Avidra does not currently support holiday schedules
* Keep after-hours SMS realistic about when your team will actually call back
* Consider extending hours slightly if your team often works late — better to have recovery active than to miss late-day leads

## Common mistakes

* Setting correct hours in the wrong timezone — everything shifts and after-hours messaging fires during business hours
* Leaving after-hours copy inconsistent with actual callback expectations
* Assuming business hours are only cosmetic — they affect message behavior
* Not updating hours when seasonal schedules change

## Related pages

<CardGroup cols={3}>
  <Card title="Workspace Profile" icon="building" href="/configuration/workspace-profile">
    Set your business identity and SMS defaults.
  </Card>

  <Card title="Follow-up Automation" icon="repeat" href="/configuration/follow-up-automation">
    Automate second-touch messaging.
  </Card>

  <Card title="Notifications" icon="bell" href="/configuration/notifications">
    Configure when alerts fire.
  </Card>
</CardGroup>
