Limitations and roadmap

NurtureSite is actively developed. This page lists known gaps so you are not surprised.

Scheduling

Feature	Status
Confirmation emails + ICS	Available (templates + RFC 5546 attachment)
Reminder emails	Available (scheduling:send-reminders hourly)
Customer reschedule	Available (/book/manage/{token})
Manual admin booking	Available (Scheduling hub)
Group / class capacity + party size	Available — inherit hours or specific class times; see Group and class bookings
Per-service waitlists (offer-to-claim)	Available — toggle on the service; see Booking waitlists
Required packages at booking (hold until signed)	Available — see Forms, waivers, and e-sign
Class packs / memberships	Not available
Shared single Google “class” event	Not available — per-attendee calendar push
Google/Microsoft calendar sync	Available (factory OAuth broker; staff connect)
Real-time calendar push webhooks	Deferred — busy cache ~5 min
iCloud CalDAV OAuth	Not available — staff use Google/Microsoft; customers use ICS email
Schedule exception admin UI	Exceptions work in engine; limited admin UI
Rich deposit editing in admin	Deposits configured per service; service price + deposit fields available
Customer invoices (balance + ad-hoc)	Available — site admin Invoices; requires Stripe Connect

CRM (site)

Feature	Status
Lead, task, deal, alert UI	Available — list named Customers / Patients / Households / Students / Leads / Guests; Deal hideable
Contacts on every record	Available — always one primary; extra people with roles, emails, phones
Consent matrix	Available — email/SMS/phone/mail × marketing vs transactional per person
Address-first matching	Available — household/place match on service address; two houses sharing a bookkeeper stay two jobs
Send audience	Available — Primary / Send-to / All contacts (provisioned per noun; never all contacts by default)
Merge duplicates	Available on record detail
Bookings and payments on the record	Available
Lead scoring rules	Available in CRM settings
Visual follow-up automations	Available — CRM → Automations (Vue Flow canvas)
Documents & e-sign	Available — Prepare workspace (compose or upload PDF); booking hold-until-signed; fill/request nodes. Not DocuSign CLM/IDV/notary. See Forms, waivers, and e-sign
Outbound email settings	Available — CRM → Settings + NurtureSite site page; see CRM outbound email
Per-node email sender	Available — site default / user / custom on Send email node
Automation health panel	Available — queue, Redis, mail driver in CRM → Settings
Mailgun sending domain	Available — platform sends from mg.nurturesite.com; BYO Mailgun still verifies records you add
Reply routing to lead threads	Available — with platform/Mailgun outbound
Enroll / stop automation on lead	Available on lead detail
Inbound webhook trigger	Available — requires public site URL
Outbound webhook node	Available — HTTPS; private IPs blocked unless allowlisted
Email open/click conditions	Available — pixel + link tracking
Reply condition	Available — tokenized Reply-To + Mailgun inbound (platform/Mailgun transport)
SMS (Conversations + automation node)	Available when Twilio is connected in CRM → Settings — see CRM outbound SMS
Email designer (templates, lead compose, automations)	Available — drag-and-drop; images upload to Media with public URLs
Lead page layout / custom fields	Available in CRM → Settings (show/hide Deal/Invoice/Notes/Documents; custom details fields)
Dry-run / live automation testing	Available in automation editor
Lead export CSV	Available at /admin/leads-export (includes contacts)
Website logins for the people you serve	Available — optional sign-in on the business website for appointments, invoices, subscriptions, and preferences. See Website logins
Invoices / Deals / Services	Keep those product names. Deal is hideable. Offering labels exist in product; Help still says Services until Scheduling shots are recaptured
Appointments / Staff	Keep those names
Word / Pages conversion	Not available — export to PDF first
DocuSign IAM, IDV, notary, bulk send, in-document payments	Not available — see Forms, waivers, and e-sign
Serial routing / kiosk UI	Schema now, UI later — see Forms, waivers, and e-sign
HIPAA mode	Automation gating + PHI consent — not a BAA or HIPAA certification. Internal nodes, including Open Dental, remain available; email/SMS/invoice/webhook require PHI communication consent; team notifications strip PHI
Open Dental patient-match node	Available on dental sites — read-only request through the NurtureSite factory broker; match by email, phone, or email then phone
PMS appointment completed trigger	Available on dental sites — a completed outcome can enroll matching automations after factory attribution
Open Dental visit starters	Available on dental sites — paused thank-you, review ask, and recall-task templates on completed visits
POS guest-match node	Available — Toast/Omnivore guest match through the factory broker
POS order lifecycle triggers	Available — placed / paid / completed / cancelled (webhooks preferred)

Practice-management software

Feature	Status
Open Dental read integration	Dental sites only — implemented and covered by automated integration tests; developer portal / Read All access granted
Dual calendar	Current — website booking uses the NurtureSite calendar; Open Dental is the practice schedule of record
Hosted Open Dental test-database proof	Pending (factory developer key + sandbox license confirmation)
Live practice connection	Not yet available — requires practice authorization and go-live review
Patient/appointment writes	Not available — parked until a paying dental design partner funds writeback
Patient portal / imaging / Practice Agent	Not available — Stage B; not this product until that gate. A website login for appointments and invoices is available separately: Website logins
BAA / HIPAA certification	Not available — do not claim a BAA or certification; HIPAA mode is automation gating only
Retained factory data	Keyed-hash patient/appointment references plus timing/status, purged after 90 days
Clinical/chart data	Not requested or retained

See Open Dental integration for scope and safeguards.

Restaurant POS

Feature	Status
Toast Standard API + partner modes	Implemented — Standard API preferred; partner marketplace behind connection_mode=partner
Omnivore adapter	Implemented — live locations require API key + ~$30/loc/mo pass-through consent
Menu / hours sync	Implemented — Menus V2 + hours push to site; V3 when ordering-partner certified
Ordering Phase A (order URL)	Implemented — Order online CTA to hosted Toast/Olo
Ordering / payments Phase B	Not available — needs partner write + credit card scopes
Food-order card processing	On Toast/Olo — NurtureSite Stripe for reservations/deposits only
Retained factory data	Keyed-hash guest/order references plus timing/status, purged after 90 days

See Toast and Omnivore POS for scope and safeguards.

NurtureSite account

Feature	Status
Scheduling glance + Connect	Available
Full appointment management in NurtureSite	Not available — use site admin
In-portal plan tier self-switch	Contact support
Instant self-serve cancel	Cancellation request workflow
Customer portal 2FA	Not available — this line is about your NurtureSite account login; use a unique password; see Account security

Analytics

Feature	Status
First-party dashboard in NurtureSite	Available
Realtime sessions	Plan-gated
Retention limits	By plan tier

Public product roadmap

Customer-facing initiatives (in progress, up next, and exploring) are published on the Updates and roadmap page. This Help Center article remains the detailed inventory of known product gaps.

Help us improve

Use Getting help to report issues or request features. Accurate feedback helps us prioritize roadmap work.

Related: Updates and roadmap, Managing appointments, Getting help.