Erste Schritte

From first login to a verified submission

Start in the Apointoo dashboard. This guide covers the hosted dashboard. To integrate the SDK in your own server, see Developers.

1. Open the right workspace

Sign in and select the business workspace. If you do not have one, follow the account and workspace creation offered on the sign-in screen. For email signup, open the verification link and sign in again to continue. Save the intake key when shown: it is displayed only once. Check the business name before changing settings: each workspace has its own integration.

In Settings, check business details, timezone and currency. Choose the flow you need: contacts, quote requests or bookings. Configure services and availability when the flow requires them. Save changes.

2. Choose who receives notifications

For email, configure the available provider, verified sender and operator notification email. This recipient can differ from the email you use to sign in. Save and check the saved value.

When notifications are disabled, records can reach the dashboard without sending email. A configured provider key does not prove delivery. For external scheduling integrations, also follow their webhook and availability instructions.

3. Connect the website form

Use your workspace's setup instructions to obtain its integration URL, slug and key. Check the website's allowed origin, including www when used. Share instructions with whoever maintains the site.

• A form that submits to the website's own route, such as /api/contact, uses a server integration. Set APOINTOO_TENANT_KEY on the server if that is the name the code reads.
• An integration calling Apointoo directly from the browser uses different configuration. Follow that integration's contract; do not swap variable names by trial and error.
• The attribution snippet captures campaign data. It does not submit your form.

In the correct hosting project, set variables for the environment you will publish. Edit an existing variable if a duplicate already exists. After saving, redeploy the website. Changing a variable does not update an earlier deployment. See Deployment.

4. Make a real submission

Open the published website and submit the form with a unique message, such as Integration test + date and time, using an email address you control. Clearly label it as a test. For bookings, use a test procedure that avoids occupying commercial availability.

In the same dashboard workspace, find the record and match the message, timestamp and submission identifier when available. If the contact already exists, check the new content and submission time; do not rely only on the lead count. A website success message alone does not prove dashboard receipt.

5. Check this submission's email

If notifications are enabled, inspect the email events associated with this test and ask the recipient to check inbox and spam.

Evidence	What it proves
Settings saved	Values were saved; the integration still needs testing
Matching dashboard record	Apointoo received this submission
Sent	A send event exists; delivery is not proven
Delivered	The provider reported delivery; inbox placement is not guaranteed
Recipient confirms receipt	The email reached the mailbox checked
No events	Delivery remains unverified; check notification mode, recipient and provider

Use events from the current test. An older email does not prove a new submission sent mail. If the form reaches the dashboard but email does not arrive, investigate notifications separately before changing the website key.

6. Finish and move forward

The contact flow is verified when the live submission appears in the correct workspace and the recipient confirms email, if notifications are part of your flow. If email is intentionally disabled, record that decision.

Google Ads is optional for receiving contacts. Connect it later and configure conversion actions for outcomes that actually happen. A received lead is neither a sale nor proof of a conversion upload. See Attribution and Conversions API.