Summer The Knowledge workspace contains the shared procedures and references used by both conversational agents and investigators. Owners and admins can edit company guides and inspect revision history. Knowledge is available during onboarding, before the company’s case runtime is enabled.
One company library, different roles
| Where | What belongs there | How to edit |
|---|---|---|
| Knowledge | Shared company facts, policies, procedures, approved answers and investigator workspace instructions. | Open a document, then Edit shared knowledge. |
| Messenger → Chat assistant instructions | The conversational role’s greeting, tone, selective reading and handoff behavior in AGENTS.md. | Select the installation and edit Conversational AGENTS.md. |
Both agents receive the full library as ordinary files under knowledge/. The conversational assistant uses native Hermes file discovery and reads only what its current question needs; deeper research belongs to the investigator. There is no separate copy of company facts to keep synchronized. See Assistant and knowledge.
Start with your company profile
New company workspaces include a telehealth starter: core rules, operational guides, proposal guidance, a clinic operating profile and starter workspace instructions. The company-specific profile begins unconfigured. It does not inherit Rebody’s products, prices, providers or policies.
Open Knowledge → company → operating-profile.md, also linked from Setup. The profile’s document ID is ops.company-profile. Review the fields relevant to your first workflow:
- Company identity, patient-facing terminology and responsible teams.
- Coverage hours, timezone and operational owners.
- Approved authenticated portal destinations and clinical escalation channels.
- Current offerings and the sources for availability and eligibility rules.
- Billing, fulfillment and support procedures needed for the selected work.
For each configured fact, record the value, source, effective or verified date, and responsible owner. Leave unresolved facts explicitly unknown. Missing unrelated sections need not block a workflow that has the evidence it needs.
Example profile entry
Paste a structure like this into the relevant part of the operating profile, then replace every bracketed field with an approved company fact. Leave anything unverified marked unknown.
### Support coverage and care referrals
Owner: [responsible team]
Source: [approved policy reference]
Last verified: [date]
Support hours: [days, hours and timezone, or Unknown]
Patient sign-in: [normal authenticated sign-in URL, or Unknown]
Clinician messaging: [normal authenticated message URL, or Unknown]
For a clinical question, direct the patient to the clinician channel above.
If the destination is unknown or unavailable, hand off to [responsible team].
Do not repeat or interpret medication directions in a support reply.
For website referrals, also put the actual URLs into the installation’s care-link settings. A URL in a knowledge document does not configure those fields.
Edit a guide
- Browse Folders, use Tags, or search for a document. Folder search includes subfolders.
- Open the document and read its current content and source information.
- Expand Edit shared knowledge.
- Update Content in Markdown and enter a Reason explaining the source or correction.
- Keep Status active, or choose retired if the guide should leave the active knowledge snapshot.
- Select Save revision and review the saved result.
If the document changed while you were editing, reload the current revision and reconcile your change before saving again. Source edit history retains earlier saved content and reasons so an authorized human can inspect how guidance changed.
The current editor updates the supplied documents. For an additional guide, a bulk import or a missing source, ask Summer to add it through your company’s setup process. There is no customer website crawler or file-upload import control on this screen.
When changes take effect
Operational agents receive a file snapshot of current knowledge when a run starts. Existing investigations retain their original snapshot. Conversational sessions refresh changed files before the next turn and keep their native history; unchanged files are reused. Check a new run or turn’s evidence before assuming it used a later correction.
Connected operational workspaces may also expose Learned lessons, with source feedback and retirement controls. Starter workspaces do not inherit another company’s learned lessons. Correct the shared guidance through the authorized workspace rather than treating a private agent note as durable company policy.
Retiring a guide excludes it from future active snapshots while retaining its revisions. Knowledge edits never waive access checks, clinical boundaries, model budgets or exact approval requirements.
Next, use Write useful guidance to turn your policies into clear instructions.