Skip to main content

​
Kinse Help Center — agent instructions

This repo powers the public Help Center at docs.kinse.io (Mintlify). Product app code lives in the separate CORA / Kinse app repo—not here. For Mintlify components, config, and writing standards:

​
About this project

  • Documentation site built on Mintlify
  • Pages are MDX with YAML frontmatter
  • Site config and nav live in docs.json
  • Preview: mint dev (from repo root)
  • Checks: mint broken-links, mint validate

​
Purpose of these docs

Help family caregivers (and people evaluating Kinse) complete tasks in the Kinse app and understand what Kinse offers. Out of scope here: marketing landing SEO (www), engineering/API/internal admin docs (app repo), deep Enterprise org-staff runbooks (point to www solutions/contact until dedicated org docs ship).

​
Product truth (do not drift)

  • Kinse = the app caregivers use. Cora = the voice on the phone call only—never brand the app as Cora.
  • Loved ones answer the phone; they need no app or new device.
  • Primary offer: phone check-ins, medication reminders, alerts, care coordination—not “AI companion” as the product label.
  • No free trial of live/outbound phone check-ins. Unpaid accounts see Choose a plan to start phone check-ins. In-app Try a check-in with Cora can work without a paid plan (no credit card; daily cap)—that is not a phone-check-in trial.
  • Plans: Essentials ($29/person/mo, $290/yr, 3 check-ins/week) and Everyday ($39/person/mo, $390/yr, 7 check-ins/week). Medication reminders uncapped on both. Price is per person called.
  • Care team members: up to 4 per person, 8 account-wide, not billed.
  • Kinse does not store call recordings; caregivers see summaries / how the call went, not full transcripts.
  • SMS alerts are not live (Coming soon). In-app alerts still show.
  • Kinse is not an emergency service.
  • Live app: app.kinse.io. Support: support@kinse.io.

​
Terminology

​
Style preferences

  • Active voice, second person (“you”)
  • Short sentences; one idea per sentence
  • Sentence case for headings
  • Bold UI labels: Click Settings
  • Prefer simple words; avoid jargon
  • No em dashes in user-facing copy (use colon, comma, or period)
  • Goal → steps → what you’ll see → related links
  • Screenshots only where the UI is easy to misread

​
Content boundaries

Do document: setup, account types (Myself / Loved one / Hybrid), check-ins, Try a check-in with Cora, voice, medications, calendar/timeline/appointments, alerts, Care Circle / care board, Insights, settings, notifications, billing, FAQ, troubleshooting, contacting support, thin privacy and care-org pointers. Do not document: internal admin (/app/admin), Edge Functions, DB schema, public API reference for engineers, secrets, exploit/debug internals, competitor comparisons by name. Do not invent: features, prices, trial offers, or HIPAA/compliance claims beyond what legal pages and product truth allow. When unsure, check the live app or ask before publishing. Keep docs.json aligned with this outline:
  1. Get started — index (What is Kinse?), quickstart, account-types, help/sign-in, help/setup-and-help
  2. Using Kinse — home, phone check-ins, check-in schedule, try-a-check-in, voice, medications, calendar, timeline, appointments, alerts, care-circle, care-board, insight
  3. Your account — people (account/care-recipients), settings, notifications, billing
  4. Help — faq, troubleshooting, message-support
  5. Learn more — privacy, care-organizations
/introduction redirects to /. Navbar primary CTA is Open app → https://app.kinse.io. When product UI changes, update copy and screenshots in the same change.

​
Before publishing

  1. Confirm claims match the live app (especially billing / no trial).
  2. Run mint broken-links.
  3. Ensure Help Center stays publicly reachable for end users when production-ready (no accidental access gate for the public Help Center).