Shared guides user manual

Open and authorize

1. Choose the app from the dashboard or its Apaleo app menu and verify the account/property context.
2. If not connected, follow the app’s installation/connection flow with an authorized Apaleo user.
3. If additional permissions are requested, use Authorize to open the full app view, review the exact Apaleo permissions and approve with the appropriate user.
4. Return to the embedded page and use Refresh page after authorization.
5. Complete the app’s onboarding and check its saved readiness state.

Choose the correct context

1. Use account context for Data and Mini administration, and for account-wide configuration and credentials.
2. Use a supported property or reservation context for scoped operational workflows. Review the active property and reservation before changing data.
3. If an action is disabled, read the role/property access explanation. An active subscription does not grant Apaleo permissions.
4. For a persistent launch problem, record the app, account/property, URL context and visible error and contact support.

Review billing

1. Open the app’s Pricing control, Manage Subscriptions or dashboard Billing as appropriate.
2. Check the exact app/property coverage, trial end and subscription/package shown for your account.
3. Review outstanding invoices, payment status and the offered Stripe payment or billing-portal link.
4. For optional AI usage, inspect the relevant app’s usage settings and billing terms before enabling paid usage.
5. After a payment or subscription change, return to the app and refresh/check the displayed access state.

Some accounts use property-level billing while others use account/package subscriptions. The displayed billing record determines coverage.

Use the actual billing view or support for prices and contract terms. The wiki does not quote account-specific prices or promise a payment grace period.

Get help

1. Use the wiki search and related articles for setup and usage instructions.
2. Ask the Contact-page support assistant a product question. It retrieves relevant articles from this same wiki and provides source links.
3. For live account investigation, email support@simultem.fi with the account/property, app, workflow and relevant reservation/profile/task/widget/automation IDs.
4. Include what you expected, what happened, the timestamp/time zone and a screenshot or exact error.

Understand the helper’s scope

1. The assistant can explain documented behavior and suggest checks.
2. It cannot inspect your live account, query customer records, run operations, verify a payment or send a support email.
3. If the wiki does not answer the question, ask the responsible administrator or support instead of treating an inferred answer as confirmed behavior.

Avoid passwords, API keys, door PINs, signed guest links, payment details and unnecessary personal data in chat.

Use the current reservation as the reference

1. Have an authorized user update the reservation dates or assigned unit in Apaleo. For an unusable room, also arrange its closure/maintenance using the property’s approved workflow.
2. Verify the reservation ID, property, arrival/departure and exact assigned unit before updating guest instructions.
3. In Tasks, review linked outstanding work, assignees, due dates and actual completion. Inspect Reservation changes policies and rule traces; check preserved manual edits instead of assuming every task moved automatically.
4. Record relevant operational changes in the task comments/history and use the configured notification channel to inform the responsible staff. Check the saved result and notification outcome.

Reconcile guest instructions and access

1. In MSG, inspect the relevant journey stages, subscribed change events, conditions, scheduled timing and Logs. A pending message does not universally reschedule or disappear after cancellation.
2. Preview the reservation-specific recipient, language and resolved tokens before sending corrected information. Already-sent instructions cannot be recalled by changing the reservation.
3. If Salto is used, verify the new unit/site/user mapping and PIN record. After a unit move, create and test a new guest link; the old link remains bound to its old unit.
4. For a date extension beyond a link’s original departure expiry, create a replacement link. Check the old unit’s physical PIN release/rotation separately.
5. Confirm the current reservation, completed/outstanding tasks, message execution and new access link individually. There is no single cross-app transfer transaction or complete reconciliation screen.

Prepare the handover

1. Review tomorrow’s reservations in the authorized reservation view and confirm property, dates and assigned units.
2. In Tasks, choose the relevant property and a due-date range that also includes earlier preparation work. Filter open tasks and inspect assignee, due date and status for each arrival.
3. Check actual guest fields and the appropriate profile/participant. Receiving an MSG form is separate from applying its fields to the reservation; verify the resulting data rather than treating submission as proof of completeness.
4. Record unresolved items, responsible staff and handover time in the relevant task comments or the property’s agreed handover record.

Review changes on the next shift

1. Recheck current reservation and task state and inspect available per-task history for changes after the recorded handover time.
2. Use MSG Logs/traces for a specific message and check its recipient/result separately from task completion.
3. Current-state reports and Overdue counts are not a snapshot of the earlier handover. Overdue counts incomplete work, not every task completed late.
4. There is no shared changes-since-handover stream or central list proving that every arrival has all required guest data. Follow the property’s checklist and investigate each outstanding item.

Define the comparison

1. Choose the hotel set, campaign identifiers and date basis: booking creation, stay dates, payment dates or task due dates measure different populations.
2. In IBE Booking Reports, the reservation query uses the IBE channel and creation-date range. Its reservation metrics do not explicitly exclude canceled reservations; check current source status and amendments.
3. In Tasks, trends use task due dates and current completion state. Status/assignee/role totals do not include an automatic promotion-attribution dimension.
4. In Data, inspect the account’s actual report page and measure definitions, property/date filters, relevant table updates and completed report refresh. Deployed measures vary by account.

Reconcile changes and limits

1. Use an explicit campaign-to-reservation linkage if attributing bookings to an offer, and a defined task linkage if measuring related workload. Separate comparable totals do not prove causal incremental business or work.
2. Recheck cancellations and amendments against current source records or a reporting measure with a documented restatement policy. Do not assume booking-created events are reversed automatically.
3. Record the refresh/as-of point, date basis, status treatment and currency used for each comparison.
4. For Excel analysis, Data exports are account-wide; apply the relevant property columns after downloading. Generated at is workbook creation time rather than a data-freshness watermark.

Read the wiki in a browser

1. Open /wiki to browse and search all app manuals without an account or Apaleo sign-in.
2. Open /wiki/<app> for an individual manual, such as /wiki/tasks or /wiki/ibe. Share an article using its #section anchor.
3. Use Browse the public wiki on the login screen to open documentation without beginning OAuth.
4. Only Open app or Sign in to apps takes you to the authenticated application. Reading the manuals requires no API connection.

Start with discovery

1. Open /api/wiki for the discovery manifest and navigation guidance.
2. Use /api/wiki/openapi.json for the OpenAPI contract, or /api/wiki/v1/tools for JSON Schema tool definitions.
3. Call list_apps to choose a manual, get_app to read its contents, search to find a topic and fetch to read the full article.
4. Search questions can use English, German or Finnish, including common app-name inflections. Articles remain in English; an AI reader can explain the fetched instructions in your language.
5. For another language or weak matches, reformulate the query in English or browse get_app. A returned match is a navigation hint, not proof that the requested feature exists.
6. Follow related article IDs for cross-app workflows and cite the returned public /wiki URLs.

GET /api/wiki/v1/search?query=send%20guest%20door%20link&app=salto&limit=5

Invoke a tool over HTTP

1. POST a tool name and arguments to /api/wiki/v1/tools.
2. Read structuredContent for machine-readable results and content for text content blocks.
3. Check HTTP status and the isError flag and correct invalid arguments using the published schema.
4. Use revision and lastReviewedAt to identify the deployed documentation version.

{"name":"fetch","arguments":{"id":"salto.guest-links"}}

Connection scope and future MCP

1. No customer login or API token is required for published wiki content; browser clients can read it with CORS.
2. The API exposes documentation only. Operational MSG, Salto and Tasks APIs require their separate credentials.
3. An AI tool must support HTTP/OpenAPI tools or a custom integration to call this API today.
4. A future MCP adapter can reuse the same tool schemas, executor and resource URIs. The HTTP discovery manifest identifies that an MCP transport is not yet implemented.

Supplying this URL to an MCP-only connector does not create a working MCP connection. MCP transport, protocol negotiation and authorization for any future private tools belong in a separate adapter.