# Contact & Booking — Which public contact and booking routes does this company publish?

Public email, phone, contact-page and booking routes with evidence.

- Capability id: `contact.find`
- Actor: `impressionable_lupine/verified-contact-booking-signals` (ID `zATaaVqLePrcoF50q`), default build `0.2.4`
- Apify Store: https://apify.com/impressionable_lupine/verified-contact-booking-signals
- Page: https://agents.retainly.dev/capabilities/contact-booking
- Last metadata check: 2026-10-08T12:16:53.713706+00:00 (read-only; not live status)

## Workflow

Enrich an account with checked business contact routes.

Simpler alternative: If you only need the contact page of one site you already know, open it directly. Choose this when you need source-checked routes as dated JSON.

Do not choose for:
- Verifying mailbox deliverability
- Finding private contact details or identifying decision-makers
- Sending messages or completing bookings

## Input

| Field | Required | Constraints | Description |
|---|---|---|---|
| `company_website` | yes | required, string, must match ^https:// | The business's official public HTTPS website. |

Minimal valid input:

```json
{
  "company_website": "https://cliniquealpa.co.uk/"
}
```

Input schema: https://agents.retainly.dev/schemas/contact-booking/input_schema.json
Report schema: https://agents.retainly.dev/schemas/contact-booking/report.schema.json

## Price and charge trigger

- Model: PAY_PER_EVENT, event `verified-contact-report` (“Verified contact report”), $0.01 USD, max 1 event per run.
- Store event description (verbatim): “Charged once for a report with source-checked public contact or booking signals. No verified signal is free.”
- Charge trigger: One event when the report contains one or more verified public contact or booking routes.
- No event when: no_verified_signal, unknown and invalid_input produce no event. No observed route is not proof none exists.
- Standard Actor platform usage included under the configuration checked on 8 Oct 2026; recheck before purchase.
- Caps are not discounts and do not guarantee a positive result. Unknown/invalid checks produce no eligible report event; caller model/workflow costs are separate.

## Statuses

| Status | Meaning | Eligible report event |
|---|---|---|
| `verified` | One or more public contact or booking routes observed on checked official pages, with source URL and timestamp. | yes |
| `no_verified_signal` | No route was observed on the checked pages. Not proof none exists. | no |
| `unknown` | The check could not reach a conclusion (for example, blocked or unsupported source). | no |
| `invalid_input` | Fix the caller input (the website must start with https://). | no |

## Evidence and limits

- Verification scope: A contact route observed on checked official website pages, with a source URL and timestamp.
- Coverage limits: This checks publication, not mailbox deliverability, decision-maker identity or completed booking. No observed route is not proof none exists.
- Request bounds: 4 requests, 6 MB total, 3 MB per page, 22-second network budget.

## Recorded example

Recorded example — observed 2026-10-08 11:43 UTC · owner-funded release test · not an independent purchase.
Subject: Clinique Alpa. Run `fZ72juVGyfOdHCHJq`, build 0.2.4. Reports may precede final event charging; their billing fields alone do not establish a settled debit.
Full report with provenance: https://agents.retainly.dev/examples/contact-booking.json

Input used:

```json
{
  "company_website": "https://cliniquealpa.co.uk/"
}
```

## Call it (after the caller authorizes spending)

Connecting does not authorize spending. Inspecting metadata never starts a run.

Inspect without purchase (MCP, anonymous endpoint `https://mcp.apify.com?tools=search-actors,fetch-actor-details`):

```json
{
  "name": "fetch-actor-details",
  "arguments": {
    "actor": "impressionable_lupine/verified-contact-booking-signals",
    "output": {
      "pricing": true,
      "inputSchema": true,
      "outputSchema": true,
      "metadata": true,
      "readme": true
    }
  }
}
```

Inspect without purchase (REST, no token):

```bash
# Free, read-only: public Actor metadata (pricing, builds). Does not start a run.
curl "https://api.apify.com/v2/acts/zATaaVqLePrcoF50q"
```

MCP `call-actor` (endpoint `https://mcp.apify.com?tools=actors,runs,storage`; run limits live in `callOptions`, never in `input`):

```json
{
  "name": "call-actor",
  "arguments": {
    "actor": "impressionable_lupine/verified-contact-booking-signals",
    "input": {
      "company_website": "https://cliniquealpa.co.uk/"
    },
    "waitSecs": 30,
    "callOptions": {
      "build": "0.2.4",
      "memory": 512,
      "timeout": 60,
      "maxTotalChargeUsd": 0.01
    }
  }
}
```

MCP follow-ups (same run):

```json
{
  "name": "get-actor-run",
  "arguments": {
    "runId": "<runId returned by call-actor>"
  }
}
```

```json
{
  "name": "get-dataset-items",
  "arguments": {
    "datasetId": "<datasetId returned by call-actor>",
    "clean": true
  }
}
```

REST API v2:

```bash
# Paid run in YOUR Apify account. Only after spending is authorized.
# Set APIFY_TOKEN securely in your client/shell; never paste it into URLs or shared files.
curl -X POST "https://api.apify.com/v2/acts/zATaaVqLePrcoF50q/runs?build=0.2.4&memory=512&timeout=60&maxTotalChargeUsd=0.01&waitForFinish=30" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"company_website":"https://cliniquealpa.co.uk/"}'
```

```bash
# Save data.id (run ID) from the first response. On timeout/ambiguity, poll THIS run.
# Never start a second charged run to recover output.
curl "https://api.apify.com/v2/actor-runs/$RUN_ID" \
  -H "Authorization: Bearer $APIFY_TOKEN"
```

```bash
# data.defaultDatasetId from the run object (one report item).
curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?format=json&clean=true" \
  -H "Authorization: Bearer $APIFY_TOKEN"
```

Recovery rule: Save the run ID from the first response; on timeout or ambiguous response, poll that same run; never start a second charged run to recover output.