Review cited assistant work before applying changes

The assistant prepares answers and proposed changes from the records you select. Generation and approval are separate steps. A ready answer does not mean a task, expense, email, or form has been created.

Select the evidence first

Open Assistant, choose the kind of work, and find the wedding, lead, client, task, conversation, form, expense, or package you want to reference. Selecting a wedding also gives you buttons to add its coordination draft, photography plan, or RSVP summary. The RSVP source contains totals, not a guest contact directory. Record access follows the current workspace and the connection's scopes.

Ask a specific question such as “Using this wedding and these meeting notes, propose the remaining florist follow-up tasks.” Read the source labels and citations alongside the answer. Stored snapshots show what the assistant actually received; a citation is a reference to that material, not independent confirmation that every sentence is correct. Long records may be truncated, and missing details belong in the uncertainties list.

Connected inbox sources stay held

An ordinary studio conversation source sends its recent message text to the configured model when you approve generation. A conversation containing linked Gmail or Outlook messages is different: its source result identifies the connected provider where available and remains unavailable for AI processing. The server repeats this check even if an API client bypasses the source picker or a mailbox message arrives after you selected the record.

This hold applies to both imported messages and messages routed through a connected mailbox, including copied history after disconnect. It runs before model usage is reserved or a model request is made. A held request can appear as failed in recent work with the reason; it does not mean its source was sent to a model. Other authorized studio records remain usable.

Provider-policy review, contractual data handling and explicit contextual sharing approval are required before expanding this boundary. Do not paste connected mailbox content into the source-text or image field to bypass it. The product does not infer provider permission from a general AI checkbox, and it does not claim account-specific training or retention guarantees that have not been verified.

Approve usage separately from changes

The displayed request price must be approved before generation. The workspace also needs enabled usage spending with sufficient room under its limit. Model credentials and the request price are part of release setup; without them, generation stays unavailable. Changing a price invalidates an older quote.

The application saves a request identity before calling the model. A repeated request with the same identity returns the existing work. If a connection fails after a model attempt, its result may be uncertain and its approved usage may still count. Open recent work before starting another request. There is no automatic model retry.

Review each proposal

Edit the proposed fields and save the edited preview. Then confirm that you reviewed that exact change and its sources. Saving an edit resets the approval checkbox. Email proposals save a private message draft by default; a separate explicit checkbox requests delivery to the displayed recipient. Delivery status appears in the conversation after queueing.

A task, appended note, pipeline stage, budget estimate, or expense is changed only after this approval. Moving a lead into a stage may start previously published automations for that stage. A receipt approval records an expense; it does not pay anyone. Forms and packages start as private drafts. The assistant has no action for refunds, card charges, public schedule publication, or form publication.

If someone changes the target after generation, the old proposal is refused. Prepare fresh work from the current record. This can also happen when two proposals touch the same source and the first changes it. The application does not silently apply the second against an outdated snapshot.

Use the companion clients

The native app and Chrome companion can select records, prepare online work, and approve supported proposals. They retain request identities after an interrupted submission. Approval always returns to the server for current permission and revision checks; cached offline work cannot apply an assistant change.

Use the web editor for complete form logic and for editing any proposed fields. Chrome directs financial and other complex drafts to the full editor. A revoked or narrowed API key loses access to historical runs whose sources require those missing permissions, as well as new actions.

Import timelines and invoices

Choose Import a timeline, select its wedding, and paste source text, import a text/Markdown/CSV document, attach a readable image or PDF, or enter a direct public HTML/text URL. Text documents are limited to 30 KB, PDFs to 500 KB; export the relevant pages of larger documents. Public URL intake does not follow redirects or sign-in pages. Model activation and approved metered usage are required for extraction.

Review each moment’s calendar date, local time, duration, location, roles, dependencies and fixed-anchor status. Add reviewed timeline moments appends to the existing draft and retains its history. It cannot publish a schedule or send change messages. Open the coordination editor for resource assignments, conflict review and publication. Existing resource-linked drafts require a named workspace member to approve an import on the web; API credentials do not substitute for that member review.

Choose Prepare an invoice to extract explicitly stated USD line amounts from a document or image. Correct every amount, due date and description against the original. Approval creates an unissued draft with no delivery, checkout or charge. Review taxes, credits and previous billing in the wedding before issuing it. Foreign currencies and ambiguous amounts must be clarified rather than converted or invented.

Review seating and meeting notes

Plan seating changes uses the wedding’s actual guest names, household labels and existing tables; this separately selected source contains more detail than RSVP totals. Approve a batch of moves after reviewing every guest and destination. The service checks current seating revision, guest/table identity and the final table capacities together, so swaps can succeed without temporarily overfilling a table. Saved floor plans are marked for renewed review when seating changes.

For Recap a meeting, select the wedding and provide its transcript or notes. The assistant can prepare an editable recap with decisions, next steps and explicitly stated preferences. Extracted preferences show an exact source quotation. Edit the summary or remove unsupported preferences, then save the preview and approve it to append to private wedding notes. Proposed tasks and messages still require separate approval. Dictated text is staged for review before insertion; browser speech support varies and uses the browser’s speech service.

Continue work and teach your writing style

Open a saved response and choose Ask a follow-up. The next request retains a link to its predecessor and includes up to eight prior turns of quoted conversation context. Current record permissions and the selected workspace sources are checked again. Earlier proposals do not authorize new actions. Reattach an original image or document when the follow-up needs a new extraction from it; historical answers are not original documents.

Use Use my edited wording as a style example on an email proposal, or Learn from these approved examples under writing preferences. Review the example, approve the model request, then review its proposed tone, greeting, sign-off, preferred length and signature. Saving those preferences is a separate action. This is explicit preference extraction from examples, not automatic model training or permission to send an email.

Keep an AI-proposed timeline alternative

Choose Explore an alternate timeline, select a wedding and its saved coordination source, and describe the alternative you want. The wedding Coordination page also opens prepared rain, shorter-celebration and photography-safe requests. Your source selection and displayed model-request cost still require approval before generation.

A Keep an alternate timeline proposal compares the saved source with every resulting adjustment. You can edit the bounded timing/location fields and save a new preview before approving. The scenario retains all original moment identities, dependencies, fixed anchors and assignment scope. Current execution, source revision and reviewed resources are rechecked at application. Unsupported locations and incomplete schedule sources stop for review.

Saving this proposal creates a named alternative version only. It leaves the current draft, published schedule, messages, signatures and payment history untouched. Open its result link to compare or restore the scenario; publishing is a separate decision. Complex scenario approval uses the full web comparison; mobile shows its scope and links to that review.

Personal notes and private conversations

Select my personal notes to find your own notebook records by text, tag or linked client name. A request containing one of these notes is private to its author before its first saved state. Its sources, answer and every follow-up remain unavailable to other workspace operators and general workspace API keys.

These conversations are read-only: they can answer or summarize, but cannot apply shared record changes or deliver messages. Removing the selected note from a follow-up does not make the conversation shared. Model usage approval and the configured provider’s handling still apply. Personal notes, privacy and recovery explains the distinction from shared CRM notes.

Compare two possible duplicate clients

Choose two CLIENT sources, then select which record would continue. This resets the draft request to a read-only comparison. You can also start from Compare these two clients with the assistant inside the CRM's existing merge review. The app never chooses a match automatically from a name or shared email address.

Approve the displayed model usage to compare the explicitly selected records. Read the matching, conflicting and missing fields alongside citations for both client snapshots and the merge boundaries. Names and contact details are evidence to inspect, not proof that two people are the same. Private personal notes are not included automatically; the client source includes only the business's CRM notes.

The response reports whether those records still match its snapshots when opened. Changed records or merge blockers are visible; an archived continuing client must be restored separately. Open current field-by-field merge review loads the current CRM values with no assistant-selected overwrite fields. Select incoming values and explicitly confirm there if you decide a merge is appropriate. Tags combine; original conversations, projects, permissions, agreements, invoices and balances stay attached to their original records. A comparison never merges a wedding or transfers money.

Native and Chrome support the same comparison and open the canonical CRM review in the browser. The browser checks your current signed-in workspace. Assistant follow-ups remain read-only even if you change the request type. Up to one client pair is allowed per comparison; long records may be truncated, so inspect the original before deciding.