Put your request forms on your website: care, transportation and questions

The three forms. Request care is a four-step wizard: Getting started (who needs care, the first name of the person who needs it, an age range, the ZIP code where care is needed, a preferred start date and the living situation), Care needs (boxes for companionship and household help, personal care, transfers, medication assistance, medication administration, insulin injections, transportation and transitional living), Your schedule (weekday days, weekday evenings, weekend days, weekend evenings, overnights, 24/7 or live-in, and hours per week) and Estimate and contact (name, email, phone, how and when to reach them, anything else). Request transportation is one page: pickup and destination addresses, pickup date and time, appointment time, one way or round trip, ambulatory, wheelchair or stretcher, the estimated wait, how often, help entering and exiting, the return time, the miles if known, then the same contact block. Ask a question is name, email, phone, how and when to reach them, and the message.

Where they live. Open Requests in your workspace and tap Put these forms on your website. The hosted pages are links you can send or put behind a button: your agency's name at the top, a small Through ExpressAgain line, the form, no ExpressAgain navigation and no sign-in. The iframes are three snippets, one per form, each with a Copy button: paste one into your own website where the form should sit; the second line of the snippet listens for the form's height so the frame grows with it and never shows a scrollbar of its own. The accent colour you set colours the buttons and the step bar on your website's copies. Your public address is set once from your agency's name, so a link on your website keeps working.

The estimate. The care form's last step and the transportation form show Estimated: and a figure only when you have typed the rate it needs under Your rates, for the estimate: the hourly rate times the hours band chosen (up to, a range, or at least), the live-in daily rate times seven for Live-in, and the ambulatory or wheelchair per-mile rate for a ride (times the miles when the person typed them, doubled for a round trip; a stretcher has no rate). Leave a rate empty and no estimate shows: the page never shows a number you did not type. Every care page says No service is confirmed until the agency reviews your request, and every transportation page says Non-emergency transportation only. For a medical emergency, call 911. Only an organization admin changes the rates and the accent.

What arrives. Each submission is one row under Requests: the kind (Care, Transportation or Questions), who sent it, a one-line summary, when, and whether it came from your website or the hosted page. Tap a row to read every answer in the form's order, the estimate the page showed, and the notes; set the status to New, Contacted, Scheduled or Closed; add a note. On a care request, Add as a client opens the same Add a client form the Patients page uses, with the name of the person who needs care and the requester's contact already filled in, so the account the agency creates is the same kind of account as any other client's. Export CSV downloads the rows the chips keep, one column per answer.

The emails and the CRM. The office gets one email per request with every answer; a care or transportation request can carry health details, so that email goes through the PHI-safe sender, and a question goes through the ordinary one. The person who asked gets a plain receipt: what happens next, in the page's words, and the estimate the page showed, with none of their answers repeated. Each request also goes out on the signed webhook to the founder's CRM as org.request.created with the agency's name and slug, the kind, the contact fields and the ZIP, never the answers.

What is never shown publicly. The public pages show your agency's name, its phone number, the accent and the rates you chose to show, nothing else. The answers, the notes and the status are read only by your agency's administrators and office, signed in. The hosted pages and the iframes set no cookie and never show a signed-in state. A suspicious submission (a hidden field filled in, a form posted faster than a person types, a link in a name) is dropped without a word to the sender, and more than five from one address in an hour are dropped too.