Question 1

What does RafterPing handle today?

Accepted Answer

RafterPing gives each workspace an inbox for valid website-form submissions sent to its webhook and for inquiries an owner records manually. Owners can track lead status, save consent details, prepare approved-template reply drafts, record appointment details, and review dated pipeline reports. RafterPing does not automatically monitor email inboxes or phone calls.

Question 2

How does a website form send a lead to RafterPing?

Accepted Answer

Each workspace has its own webhook URL and secret. The workspace owner copies the URL and generates the secret in Website-form setup, then configures the website form provider to send submissions to that URL from its server using the secret. The secret can be sent in the X-RafterPing-Secret header or as a Bearer token. Keep it in server-side settings; do not expose it in browser code. The owner must configure the form provider, and the source is marked connected after its first valid submission. Invalid secrets or incomplete lead details are rejected.

Question 3

Does RafterPing read my email inbox or detect missed calls?

Accepted Answer

No. RafterPing does not read a mailbox or detect calls. A workspace owner can manually enter an email inquiry, which is saved as an owner-reported lead. Saving it does not connect email, create a reply, or send a message. Missed calls can also be recorded by an owner; they are not detected automatically.

Question 4

How is a contact’s consent recorded?

Accepted Answer

A lead can be marked as given, declined, or unknown. When an owner records given or declined, the workspace asks them to confirm they have direct evidence. The inquiry text by itself does not establish consent. Reply-draft generation and copying require explicit recorded consent; they are unavailable when consent is unknown or declined, evidence is missing, or the lead has opted out.

Question 5

What are saved reply drafts, and are they sent automatically?

Accepted Answer

For an eligible lead with explicit current consent, RafterPing can prepare and save a draft from the workspace owner’s approved reply template and the lead’s saved details. The owner reviews and copies the draft for manual use. RafterPing does not send the draft by email, text, or another messaging connection.

Question 6

Can RafterPing book or track appointments?

Accepted Answer

An owner can set weekly appointment windows and record an appointment on a lead with its date, time, and timezone. Afterward, the owner can record whether it was completed. These are workspace records: RafterPing does not check or sync an external calendar or book appointments automatically. For a scheduled appointment, RafterPing sends one reminder email to the homeowner 24 elapsed hours before its saved start instant when the lead has a usable email address, explicit contact consent with a recorded evidence timestamp, and is not opted out. The reminder uses the appointment’s saved timezone. Existing confirmation, reschedule, and cancellation emails remain immediate and use the same consent checks. An owner’s next-follow-up date is a separate owner workflow and does not send an email to the homeowner.

Question 7

What appears in a daily pipeline report, and who sends it?

Accepted Answer

A dated workspace snapshot summarizes saved leads by status and source, along with recorded appointment counts and outcomes. The current day’s snapshot is saved or refreshed when the workspace report loads; dates use UTC, and earlier saved snapshots can be reviewed. A workspace owner can select a report and choose Email report to send that snapshot to their account email. Report emails require that owner action and are not sent automatically.

Question 8

Which sources and connections should I expect to be available?

Accepted Answer

The automated intake described here is the workspace-specific website-form webhook after the owner configures their form provider. Email inquiries and missed calls are owner-recorded. This FAQ does not claim a mailbox, phone, CRM, calendar, or messaging connection; treat another source as unconnected unless the owner has configured it and the workspace shows it connected.