> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/scheduling-services-and-payments/scheduling-services-and-payments.md).

# Scheduling, Services and Payments

ScribeWare 7 handles the work that surrounds an inspection, not just the report. A client can book on your website, receive an agreement, sign it, pay, and land on your calendar with the report already started.

All of it is set up from **Settings**, under the SCHEDULING and MESSAGING headings — plus the optional Google Calendar connection under INTEGRATIONS.

<figure><img src="/files/y4GwJP1V05st5abrVFIG" alt="Cycling through the scheduling, services, contracts, messaging and invoicing settings pages"><figcaption><p>The six settings pages behind scheduling, services, contracts, messages and payments</p></figcaption></figure>

New to this? Start with the walkthrough — it sets everything up in the order that works.

{% content-ref url="/pages/w4r38OGUzE15o9I4m5l9" %}
[Getting Started with Scheduling](/scheduling-services-and-payments/scheduling-services-and-payments/getting-started-with-scheduling.md)
{% endcontent-ref %}

## The Pieces

{% content-ref url="/pages/EobKz0NZ2ZDUiprLtzq1" %}
[Services and Pricing](/scheduling-services-and-payments/scheduling-services-and-payments/services-and-pricing.md)
{% endcontent-ref %}

{% content-ref url="/pages/s1p9dY9cFZkBvdKQW36P" %}
[Contracts](/scheduling-services-and-payments/scheduling-services-and-payments/contracts.md)
{% endcontent-ref %}

{% content-ref url="/pages/Yfkni1X5d2pXt4hCX2y6" %}
[Message Templates](/scheduling-services-and-payments/scheduling-services-and-payments/message-templates.md)
{% endcontent-ref %}

{% content-ref url="/pages/n0QUP0Hul3nE99SQG30B" %}
[Message Automations](/scheduling-services-and-payments/scheduling-services-and-payments/message-automations.md)
{% endcontent-ref %}

{% content-ref url="/pages/BN1qAEPb1yYrcvsLjvuD" %}
[Client Invoicing and Payments](/scheduling-services-and-payments/scheduling-services-and-payments/client-invoicing-and-payments.md)
{% endcontent-ref %}

{% content-ref url="/pages/kVc7j4HDWm8meKIYeTmq" %}
[Google Calendar](/scheduling-services-and-payments/scheduling-services-and-payments/google-calendar.md)
{% endcontent-ref %}

## How They Fit Together

Each piece feeds the next, which is why the walkthrough covers them in order:

* **Services** decide what a job costs and how long it takes. That drives the invoice, the calendar, and the price a client sees when booking.
* **Contracts** attach to services, so the right agreement lands on the right job automatically.
* **Message templates** carry the links your client uses to sign and pay.
* **Automations** send those templates on a schedule so you're not chasing people by hand.
* **Invoicing and payments** close the loop, and can hold a report back until the client has signed and paid.
* **Google Calendar** is optional, and connects the whole thing to the calendar you already live in.

Your day-to-day view of all of it is the home screen calendar.

{% content-ref url="/pages/cA26mYp34dsGshQKRvz7" %}
[The Desktop Calendar](/getting-started/the-desktop-calendar.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scribeware.com/scheduling-services-and-payments/scheduling-services-and-payments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.