Attachment card parsing — shared rendering across chat and search
ZenChat displays Smartshare attachment cards — such as invoice cards, ePrescription cards, and appointment cards — identically whether a card appears inside a conversation or in a global search result. This article explains how that shared rendering works, how guest names are resolved on cards, and what happens when a card's data cannot be parsed.
Audience: Employees who use ZenChat on the Zenoti web platform or the MyZen app and who share or receive Smartshare record cards.
Before you begin
ZenChat must be enabled at your center. Contact your administrator if you do not see ZenChat in Zenoti.
To view and interact with ePrescription cards, your center must have the ePrescription card feature enabled. This feature is flag-controlled and may not be active at all centers. Contact your administrator to confirm availability.
Availability: The ePrescription card requires a feature flag enabled at your center. Contact your administrator if ePrescription cards do not appear for your center.
Shared record cards respect each recipient's security role. If you do not have access to a record, you cannot view its full details even if someone shares the card with you.
ZenChat is available on the Zenoti web platform and on the MyZen app. It is not available on ZMA.
Steps
Understand how card rendering works across chat and search
ZenChat uses the same card models to display Smartshare attachment cards in both places where cards appear:
- Inside a conversation — when a colleague shares an Invoice, Appointment, or ePrescription record via Smartshare, the card is rendered in the message thread.
- In global search results — when you search for a message that contains an attachment card, the card displayed in the search result row looks exactly the same as it does inside the conversation.
Because both surfaces use the same underlying card model, you do not need to open the full conversation to interpret the card. The information shown — card type, record details, and guest name — is consistent in both views.
Note: ZenChat is employee-to-employee messaging. Smartshare cards share Zenoti records such as guest profiles, appointments, and invoices between colleagues. For guest-facing messaging, see HyperConnect for guest-facing messaging.
Understand how guest names appear on cards
When an invoice card or ePrescription card displays a guest's name, ZenChat resolves the name using a two-step fallback:
- Preferred: ZenChat uses the guest's individual first name and last name fields when those enriched values are available.
- Fallback: If the individual first and last name fields are absent or empty, ZenChat uses the composite guest name field stored with the record.
This means the name on a card reflects the most complete guest information available at the time the card is rendered. You do not need to take any action to trigger this resolution — it happens automatically whenever a card is displayed.
Note: The name displayed on the card is resolved at render time. If a guest's profile was updated after a card was originally shared, the name shown may reflect the current enriched fields rather than what was visible when the message was sent.
Understand what happens when a card cannot be parsed
Occasionally, an attachment card's data may be incomplete or in an unexpected format. When this occurs:
- ZenChat silently drops only that card row.
- No error message is displayed.
- The rest of the message or search result — including any text, other cards, or other attachments — remains fully visible.
You do not need to take any action when a card fails to render. If you need the underlying record, navigate to it directly from the relevant module in Zenoti (for example, open the invoice from the guest's profile or from the Point of Sale).
Tip: If you consistently see a card missing from a shared message, the record may have been created with incomplete data. Ask the colleague who shared it to verify the record and reshare using Attach a Zenoti record to a message.
Work with ePrescription cards specifically
ePrescription cards have additional behaviors depending on the platform you are using:
- Zenoti web: Selecting an ePrescription card opens the full Prescription Detail view, where you can take actions on the prescription based on your access.
- MyZen app: The ePrescription card is viewable as a card only. Opening the Prescription Detail view is not supported on the MyZen app.
If you open a Prescription Detail from an ePrescription card and the prescription belongs to a center you do not have access to, the Re-prescribe, Resend Reminder, and Mark as Refill Denied actions are displayed as disabled. You can view the card details but cannot act on the prescription.
If you are not yet onboarded to ePrescribe at the relevant center, only the Re-prescribe action is disabled. Other actions remain available based on your normal access permissions.
Availability: ePrescription card functionality requires both the ePrescription card feature flag to be enabled at your center and appropriate access to the ePrescribe feature. Contact your administrator if actions appear unexpectedly disabled.
Tips
- Check global search first for recent records. Because search results render the same card models as conversations, you can quickly verify card details — such as invoice amounts or appointment times — directly from search without opening each conversation.
- Use the direct navigation path for missing cards. If a card does not render in a message, go directly to the record in the appropriate Zenoti module rather than asking the sender to reshare immediately. The underlying record is unaffected by the card not rendering.
- Note platform differences before routing colleagues. If your team includes both web and MyZen app users, remind app-based staff that ePrescription detail actions are not available on MyZen. Route prescription follow-ups to colleagues working on Zenoti web.
- Verify center access before sharing cross-center records. If you share an ePrescription card for a prescription from a center the recipient cannot access, they will see the card but all key actions will be disabled. Share records from centers where the recipient has active access.
Troubleshooting
A card I shared is visible in my conversation but does not appear in the recipient's search results.
Search indexes attachment cards after a message is sent. If the recipient searches immediately after the message is delivered, the card may not yet be indexed. Ask the recipient to wait briefly and search again. If the card still does not appear, verify that the record was successfully shared by checking the message in the conversation.
An ePrescription card shows the correct guest name in the conversation but a different name in the search result.
Both views use the same name resolution logic. If the names differ, the guest's profile may have been updated between when you viewed the message and when the search result was rendered. The card always shows the most current resolved name. This is expected behavior and does not indicate a data error.
I expected a card to appear in a message but the card row is missing entirely.
When a card's data cannot be parsed, ZenChat removes that card row without displaying an error. The message text and any other content remain intact. To retrieve the record, navigate directly to it in the relevant Zenoti module. If the issue recurs with records from the same source, contact your administrator to verify the record data is complete.
On MyZen, I tapped an ePrescription card but it did not open the Prescription Detail view.
Opening Prescription Detail from an ePrescription card is not supported on the MyZen app. To access the full Prescription Detail and take actions on the prescription, open Zenoti on a web browser and locate the card in the conversation or via search.
Actions on a Prescription Detail opened from an ePrescription card are disabled.
Two conditions can disable prescription actions:
- If the prescription belongs to a center you do not have access to, the Re-prescribe, Resend Reminder, and Mark as Refill Denied actions are all disabled.
- If you are not onboarded to ePrescribe at the relevant center, only Re-prescribe is disabled; other actions follow your normal access rules.
Contact your administrator to resolve access or onboarding issues.