Frequently asked questions

It tells you whether a client’s enquiry path worked beyond the ‘Thank you’ page, and gives your client proof they can act on. Pathquill is lead-delivery assurance for web and marketing agencies: you run it across your client portfolio, and can include it in a website-care plan, so client enquiries aren’t silently lost. The form or quote request submits, the enquiry reaches the client’s inbox or CRM, and the customer’s auto-reply goes out. When a step breaks, you get an alert and evidence so you can fix it before the client loses a lead.

Today, in the pilot, Pathquill proves the first two steps with clearly labelled test enquiries and produces a shareable evidence page for every check. Auto-reply checks and client-ready branded reports are coming.

Web and marketing agencies that look after client websites. We’re starting with agencies responsible for high-value forms in legal, medical, finance, home services, and B2B quote requests, where one lost enquiry really matters.

Every test enquiry carries a unique, unguessable pq-run-… token. The receiving system relays that token back to Pathquill, either through an authenticated webhook from your inbox or CRM, or by forwarding the test email to a Pathquill address handled by Cloudflare Email Routing. If the token comes back, the check passes; if it doesn’t, the check fails and the evidence shows which stage went wrong.

Standard HTML forms on HTTPS pages that submit with POST. Forms protected by a CAPTCHA or a login, forms that only appear after JavaScript runs, and forms that don’t submit with POST aren’t supported yet — Pathquill reports those as unsupported rather than guessing. It never tries to get around CAPTCHA or bot protection.

1. Zero-config inspect (free, coming soon): a no-setup check of the public form, the browser request and response, validation, spam protection, and the visible confirmation. It isn’t live yet; apply to join the waitlist.

2. Proof of handoff (live in the pilot): an authorised webhook, CRM workflow, or email-token route proves the test enquiry was delivered beyond the browser.

3. Continuity monitoring (paid, roadmap): watches real enquiry counts and flags “no new enquiries” anomalies, such as no leads in 48 hours when a client usually gets ten, without storing lead contents. It will only be switched on with the agency’s and the client’s consent.

Manual or scheduled checks that send a clearly labelled test enquiry through an authorised contact or quote-request form, prove it reached the inbox or CRM by matching its token, and produce an evidence page. Scheduled checks, and signed alerts to your webhook when one fails, are switched on per client site once you and your client have agreed.

Not live yet: the free zero-config inspect; a client-ready branded report (your logo, date, form URL, outcome, evidence, limitations, and recommended next action); a “Create support ticket” action on every failed report, with safe evidence attached; confidence labels on results; checking the customer’s auto-reply; checking that the right fields arrived; and email alerts.

Integrations come in this order: WordPress forms (Gravity Forms and Contact Form 7), webhooks, Zapier and Make first, then HubSpot as the first named CRM, then Pipedrive. Booking tools such as Calendly come later. Paid continuity monitoring is on the roadmap after that; see the Privacy Policy.

Coming soon: every result will carry one of five labels so you and your client know how strong the evidence is.

Observed: Pathquill saw it happen itself, for example the form loaded and accepted the submission.

Reported: another system told Pathquill it happened, but Pathquill didn’t see it directly.

Delivery-proven: the test enquiry’s unique token came back from the client’s inbox or CRM, so delivery is proven.

Inferred: a likely conclusion drawn from other signals, not directly seen or proven.

Unknown: Pathquill couldn’t tell, and says so rather than guessing.

Today results show as passed, failed (with the stage that failed), or unsupported. A pass means delivery was proven by token.

Anything that can post the test token to Pathquill’s authenticated webhook, including a Zapier or Make step or a CRM workflow, or a rule that forwards the test email. WordPress plugins such as Gravity Forms and Contact Form 7 work when the form is a standard server-rendered form; dedicated plugin support is planned.

So nobody mistakes them for real leads, test enquiries use the name “Pathquill synthetic tester”, the email address pathquill.synthetic@example.invalid, and the message “Authorised Pathquill synthetic enquiry. Test token: pq-run-…”. Subject fields read “Pathquill synthetic enquiry pq-run-…”. You can set up an inbox or CRM rule on these labels to route or tag them.

Yes. You may only test forms you own or are authorised to test by the website owner and the owner of the receiving inbox or CRM. Before a test runs, Pathquill asks you to confirm that authorisation. See the Acceptable Use Policy.

Not today. Pathquill doesn’t connect to, poll, or ask for OAuth access to Gmail, Google Workspace, Microsoft 365, or your CRM. It only learns about the specific test enquiry that the receiving system sends back. The planned read-only connection for continuity monitoring will be optional, only enabled with your and your client’s consent, and will count enquiries without storing their contents.

A free, hands-on pilot for a small number of web and marketing agencies. We set up proof-of-handoff checks on your clients’ enquiry forms together, and you help shape what gets built next. At the end we score the pilot together on four things: a useful finding, report clarity, your time to operate it, and willingness to pay. If Pathquill becomes a paid product, we’ll set out pricing in writing first. Apply here.

Not yet. Pathquill is early-stage and the pilot is hands-on and run by the founder. It is free, provided as is, and has no SLA. See the Pilot Terms.

Not yet — public sign-up is turned off while we run the pilot. Apply for the pilot and we’ll set things up with you.

Today, only what it needs: the form addresses you configure, run tokens, timestamps, status codes, and outcomes. It doesn’t store form response bodies, webhook payload contents, or forwarded email contents. If you apply for the pilot or send a suggestion, we keep what you submit. The Privacy Policy has the details, including the overseas providers we use.

On Cloudflare (Workers and the D1 database). Service emails are sent through Resend, and our mailboxes are hosted by Zoho. See the Privacy Policy.

Questions, privacy requests, or security reports: support@pathquill.app. Pilot conversations: pilots@pathquill.app. Or use the suggestion form below.