Skip to content
Inlet

FORM DELIVERY, VERIFIED

Your form says sent. Did the enquiry arrive?

Inlet tests your website’s enquiry forms, checks whether each test reaches the right inbox, and helps your developer fix failures in the code.

Run a live exampleSee how it works

Built for developers and agencies maintaining business websites.

Contact form — acme-demo.testSample environment. Example workflow
What the website showedWhat the destination receivedArrived

The upper line is what the website showed. The lower line is what the destination received.

  1. Browser submitted

    The form said the enquiry was sent.

    Done

  2. Checking inbox

    Looking for this test's unique ID at the destination.

    Done

  3. Receipt confirmed

    The matching message was found in the connected inbox.

    Received

THE PROBLEM

A success message can hide a lost enquiry.

A visitor submits a request. The website says it went through. But if the notification fails, the business might never see it. Ordinary uptime checks won’t catch that gap.

  1. 1

    Customer sends a request

    A visitor fills in the form and presses send.

  2. 2

    Website displays “Sent”

    The page confirms it. The visitor moves on.

  3. 3

    Inbox receives nothing

    A possible failure: the notification never arrives, and nobody is told.

Inlet checks the step that the success message can’t prove.

FROM TEST TO FIX

One check, from the browser to the inbox.

Inlet follows the same route a customer would take, then keeps going until it can tell you what happened.

  1. Browser journeyExample
    Form
    Contact form
    Name field
    Inlet Test Enquiry
    Email field
    inlet-test@example.test
    Test ID
    INLET-TEST-••••
    Submit
    One click, never repeated
  2. Delivery resultExample
    Destination
    Connected inbox
    Searching for
    INLET-TEST-••••
    Observation window
    30 seconds
    Result
    Received
  3. InvestigationExample
    1. Read submission resultDone
    2. Checked destinationDone
    3. Located notification handlerDone
    4. Created candidate patchDone
  4. Proposed changeExample
    src/lib/settings.ts- recipient: env.NOTIFY_EMAIL,+ recipient: env.NOTIFY_ADDRESS,
    Unit tests and build
    Passed
    Private preview inbox
    Received
    Developer approval
    Required
  5. After deploymentExample
    Original check
    Not received
    New check, new test ID
    Received
    Incident
    Verified recovered

See the failure. See the evidence. See the fix.

Every result links back to the browser action, delivery check, and exact code change. No guesswork hidden behind a green status light.

Form submitted. Enquiry not received.Read-only example

Browser event

Form submitted
Yes
Success message
Displayed
Response
200

Inbox observation

Destination
Reachable
Observation window
30 seconds
Matching message
None

Patch checks

Types and build
Passed
Unit tests
Passed
Preview delivery
Received

A record you can inspect

Screenshots, timestamps, correlation IDs, run events.

A patch your developer can review

Changed files, tests, approval status.

FOR TEAMS THAT OWN THE CODE

Look after every client’s enquiry forms in one place.

Add the forms you maintain, choose how often to check them, and get a clear record when delivery changes. If a source-code issue is found, the proposed repair stays in your review process.

Multiple client sites
Each form has its own destination and schedule.
Shared responsibility
Owner, maintainer and viewer roles.
Change history
See what failed, what was approved, and which run confirmed recovery.
Notifications with context
Alert on failure and recovery, not on every successful check.
WebsitesSample sites

  • Harbour Dental

    Book an appointment

    Received

    In 6 hours

  • Northgate Joinery

    Request a quote

    Not received

    Incident open

  • Marlow Architects

    Contact us

    Unverified

    Reconnect inbox

The agent can test a fix. You decide what ships.

Browser runs and code tests happen in isolated execution environments. The agent works with a restricted copy of approved files, and you review the proposed change before it reaches production.

Limited access
Test only verified websites and allowed repository paths.
Independent checks
Browser success is compared with a destination receipt.
Developer approval
Inspect the diff and test results before merge or deployment.
Proposed fixExample

Proposed fix

  • Type checks
  • Unit tests
  • Build
  • Preview delivery

Developer approval required

Nothing is merged or deployed until a person with approval rights accepts this change.

Awaiting approval

Try the check before you connect a website.

Use our controlled test site to watch a form submission, the delivery check, and the result. You can also see how Inlet responds when the notification is deliberately broken.

Open the live example

The example uses a test website and test mailbox. No customer information is involved.

  1. Preparing1 of 5
  2. Opening form2 of 5
  3. Submitting3 of 5
  4. Checking delivery4 of 5
  5. Result5 of 5

Questions

Know whether your next enquiry arrived.

Start with the live example, then connect the forms your team maintains.

Run a live exampleCreate workspace