Skip to content

new-inquiry

Source of truth: packages/notifications/src/translations.ts

DomainChannelsRecipients
chatin-app + email + pushAgent assigned to the property
SourceContext
packages/api/src/services/chat.ts:271createOrGetChannel
interface NewInquiryData {
customerName: string;
propertyAddress: string;
listingUrl: string;
message: string;
/** Optional property card fields */
propertyImage?: string;
propertyPrice?: string;
propertyType?: string;
}

The caller invokes triggerWorkflow('new-inquiry', recipientIds, data) where data is the NewInquiryData shape above. The server pre-translates the payload via getTranslatedPayload('new-inquiry', recipientLocale, data) from @repo/notifications before sending, producing { inAppBody, emailSubject, emailBody } for the dashboard templates to render.

Knock dashboard template body: {{ inAppBody }}.

LocalePreview source
es💬 Nueva consulta de ${p.customerName} sobre ${p.propertyAddress}
en💬 New inquiry from ${p.customerName} about ${p.propertyAddress}

Subject: {{ emailSubject }}. Body: {{ emailBody }} (HTML mode, dashboard escaping OFF — every user-supplied string is escaped server-side via escapeHtml from @repo/notifications).

LocaleSubject preview
esNueva consulta sobre tu propiedad en ${p.propertyAddress}
enNew inquiry about your listing at ${p.propertyAddress}

Email body is composed by emailBody.es in packages/notifications/src/translations.ts via the layout components in packages/notifications/src/email-layout.ts (wrapEmailLayout, ctaButton, calloutBox, quoteBlock, propertyCard, detailTable / detailRow). Body source is not inlined here because it spans tens of lines per locale — open the source file for the full template.

Push delivery is configured at the Knock dashboard level for this workflow (FCM channel step with {{ inAppBody }} as the notification body). iOS APNs is deferred until the dashboard p8 key is wired — see Configuration → mobile push.