0041: Quotes on the better-supabase quotes block
Quote storage, creation, line edits, sending, publishing, withdrawing, every answer and invoicing a quote run on the better-supabase quotes and invoices blocks over CentraKit's own tables, and both document state machines write their own history.
Agent notes
Things coding agents get wrong in CentraKit, grouped by topic.
0041: Quotes on the better-supabase quotes block
Quote storage, creation, line edits, sending, publishing, withdrawing, every answer and invoicing a quote run on the better-supabase quotes and invoices blocks over CentraKit's own tables, and both document state machines write their own history.
Agent notes
Things coding agents get wrong in CentraKit, grouped by topic.
An organization connects several WhatsApp numbers through Meta Embedded Signup with coexistence. A business number is shared with the team, a personal number is visible to its owner only, and personal WhatsApp accounts outside the Business Platform are not supported.
The inbox connects WhatsApp through the Cloud API with credentials the customer copies from their own Meta app: phone number id, access token, app secret and verify token. Each connection has its own webhook URL with the organization and connection ids in the path. That works for technical customers, but a care organization or a small business cannot set up a Meta app.
Customers want two kinds of numbers in one organization:
The connect form already offers a scope of organization or user, but only integration_installations stores it. inbox_connections and inbox_threads have no owner, their select policies admit everyone with chat.read in the organization, and the Realtime trigger broadcasts every thread change on org:{organizationId}:inbox. A personal number is therefore readable by the whole team today.
Meta only offers WhatsApp to software through the WhatsApp Business Platform. A consumer WhatsApp account can only be reached through unofficial WhatsApp Web bridges, which break the WhatsApp terms and risk a ban of the number. Since 2025 Embedded Signup can onboard a number that already runs the WhatsApp Business app ("coexistence"): the owner keeps the app on their phone and the platform receives and sends the same conversations.
organization: every member with chat.read reads its threads, and members with the reply permission answer them.personal: only the owner (owner_user_id) reads and answers its threads, unless the owner explicitly shares a thread with the team or named members. Every member with chat.create may connect their own work number. Organization admins see the connection's name, number, status, health and usage figures, so they can manage, bill and disconnect it, but never its threads, messages, contacts derived from it or AI summaries. AI auto-reply runs only when the owner turns it on; otherwise the AI suggests replies the owner approves.inbox_connections gets visibility and owner_user_id; every table and function that exposes thread content filters on one set-based helper that returns the connection ids the caller may read. Realtime, search, notifications, the AI assistant, MCP tools, the REST API, workflows and exports use the same rule.phone_number_id, which is unique across the platform. The per-connection URL stays for connections made with own credentials.whatsapp_business_management and whatsapp_business_messaging before customers can use Embedded Signup. That lead time is outside our control.Last updated on
0041: Quotes on the better-supabase quotes block
Quote storage, creation, line edits, sending, publishing, withdrawing, every answer and invoicing a quote run on the better-supabase quotes and invoices blocks over CentraKit's own tables, and both document state machines write their own history.
Agent notes
Things coding agents get wrong in CentraKit, grouped by topic.