Skip to main content

Build a patient enrollment Site with Team Bot

Use your Team Bot to plan a public Site that explains a care program and lets visitors request a callback. Use Workspace Manager to set up the data that staff use to review requests. A receipt confirms that a request was received. Staff review, consent, program enrollment, and appointment booking each need their own steps. For a phone campaign’s opt-in Site, see SMS consent setup.

Choose the Workspace and audience​

  1. In the right Organization, open Bots, select your Team Bot, and choose New Chat. Use a private Gravity Rail Chat.
  2. Pick a test Workspace. Ask an Organization admin to confirm it is included under the Bot’s Workspace access. You also need permission to configure Sites and Data Types. The staff reviewer needs permission to read Public Form submissions. Bot Workspace access · Site permissions · Public Forms
  3. Replace the bracketed names in the prompts. Use synthetic examples in the test Workspace. Keep staff review in the Workspace app or on a Members Only Site restricted to the intended staff roles. If patients need to sign in and see their own status, build that as a separate signed-in flow using Member-owned records.

Send to Team Bot:

Use [Organization] and [Test Workspace]. Look for an existing Site and Public
Form named [Program Requests] before planning changes. Draft a public program
overview and a “Request a callback” page. Propose a Public Form with a name and
one approved callback method. Tell visitors, “We received your request. Our team
will contact you about next steps.” Specify who checks Submissions and who makes
an enrollment decision. Use synthetic examples. Leave publishing and sharing
for my review. Give me links to resources you verified, and identify any step
I need to take in Workspace Manager or Sites.

Set up the Form and staff data​

If Team Bot returns a plan without saved links, ask it for a handoff:

Write a handoff I can paste into Workspace Manager. Include the Workspace,
the approved page and field requirements, any saved links you verified, and
the first setup step that still needs to happen.

Open the named Workspace and select Manager from the sidebar. Use Ask for approval to review each proposed change. You can also create the Form under Knowledge → Data → New Data Type → Public Form. Choose Public Form at creation and note its identifier. Staff will review its read-only Submissions tab. Assign a reviewer before launch because each request needs a human follow-up. Use the Manager · Create a Public Form

Send to Workspace Manager:

In this test Workspace, find or create the Public Form [Program Requests].
Reuse the existing Form if it matches. Use the reviewed fields for name and
callback method. Show me field types, required fields, and the saved Form link.
Keep the submission list for authorized staff. Separately, propose a Member
Table [Program Review] for staff to use after matching a request to the right
Member. Track review status, consent, and the enrollment decision separately.
Show me the proposed fields and wait for approval before creating that table.
Keep publication, sharing, and enrollment actions for separate review.

If the Manager reports that it saved a Form or Data Type, open the link and check Fields and Settings. If it reports a Workflow is saved, open the Workflow and check its Tasks and status separately. A Public Form submission does not create a Member or start a Workflow. Staff match the request to the right Member and use the authorized enrollment process.

Build and publish the Site​

Paste the Site and Form links into the Manager Chat and ask it to prepare the Site. The Manager can prepare a draft Site shell and pages when its Site tools are available. Custom source, the Form binding, and live publication each need their own check. If you receive a draft or a build error, use the returned handoff to continue in Sites with a builder who can edit a source Site. Adding a page to a managed-theme Site does not attach a Public Form.

Use [Site name or link] and [saved Public Form link] in this Workspace.
Prepare the source Site with the approved program overview and callback page.
Use AnonymousForm from @gravity-rail/react to submit to that exact Form.
Show the receipt after successful submission and a retry message on failure.
Keep patient and staff records, credentials, and private Files out of the public
Site. Leave anonymous Reading Records disabled. Give me the saved Site or source
link, preview, intended audience, and Form binding. Ask before publishing. If
you cannot save or preview the Site, give my builder the draft and the specific
step to finish.

Review the saved source in Preview. In Access & Permissions → Publishing and sharing, check that only the intended public Site is public. Publish the source from Publish in the Site header and wait for the build to succeed. Open the live URL returned by Sites. For a custom domain, use the verified domain. Publish a source Site · Embed a Public Form

Verify the published Site​

  1. Open the live URL in a signed-out browser. Check the overview, callback link, form labels, and validation. Confirm that the visitor cannot open staff pages or read records.
  2. Submit a single synthetic request with a unique test name. Check that the browser shows the receipt only after submission succeeds.
  3. As an authorized staff reviewer, open Knowledge → Data → Public Forms → [Program Requests] → Submissions. Reload and verify there is exactly one row for your test. If the test includes staff follow-up, check that the reviewer can record their decision in the correct synthetic Member’s record.
  4. If you also built a signed-in patient flow, test with two synthetic Member accounts. Each should reach their own permitted information. Verify the patient-visible status after staff review if your flow promises an update.

Send to Team Bot, using only test evidence you have permission to share:

For [Workspace] and [live URL], summarize launch checks from these results:
[published revision, test time, receipt result, matching submission count,
staff access result]. Give each check a pass, fail, or untested result and
name the evidence. A preview or a draft is not proof of a live submission.
If the receipt and staff record disagree, name the next check and the owner.
Leave out submitted values and patient details.

Maintain the Site and report results​

For copy changes, give Team Bot the current live URL and the exact text to revise. For changes to a Form or a Data Type that already holds records, ask the Manager to review existing fields and their uses first. Prefer adding an optional field when that meets the need. Changes to required fields, field types, option values or slugs can affect older records, Site code and Workflows. Test any planned change in the test Workspace before applying it. Public Form submissions are read-only. Field settings

Review [Site link], [Public Form link], and [Program Review Data Type link].
Propose [change]. Show which existing fields, records, and Workflows it affects
and give me a test for old records and one for a new submission. Keep existing
values and access intact. Give me the saved draft or setup steps, and wait for
my approval before updating live source or moving existing data.

Recheck the published visitor flow and staff destination after releases. For a report, use your authorized staff view to count submissions and the approved enrollment record source to count completed enrollments. Supply aggregate totals if the Bot cannot read a source. Count repeat submissions as requests unless you have a documented way to match them to unique people.

For [Workspace] from [start date] through [end date] in [time zone], report
requests received, reviews completed, and confirmed enrollments using these
approved totals or accessible sources: [totals or links]. Name the source,
date basis, and counting rule for each number. Mark missing counts unavailable.
Leave out patient details. Calculate an enrollment rate only if confirmed
enrollments and eligible requests are matched for the same group.

If a step is blocked, ask the Bot or Manager for the exact operation it could complete, any saved links, and the step that needs an authorized builder. If that builder can reproduce a product problem, ask the Bot to file a support request with the operation, test time, and error, using synthetic evidence. Track work and get support