--- title: "Write with AI" url: https://www.tallievents.com/docs/write-with-ai updated: 2026-11-06 site: "Talli" --- ### All guides #### [Docs home](https://www.tallievents.com/docs) #### Getting started - [Getting started](https://www.tallievents.com/docs/getting-started) - [Organization settings and branding](https://www.tallievents.com/docs/branding) #### Venues and layouts - [Venues](https://www.tallievents.com/docs/venues) - [Floor plans and layouts](https://www.tallievents.com/docs/floor-plans-and-layouts) - [Venue map and signs](https://www.tallievents.com/docs/venue-map-and-signs) - [One layout across a series](https://www.tallievents.com/docs/series-layouts) #### Events - [Events](https://www.tallievents.com/docs/events) - [Agenda](https://www.tallievents.com/docs/agenda) - [Write with AI](https://www.tallievents.com/docs/write-with-ai) - [Cloning events](https://www.tallievents.com/docs/cloning) - [Languages and translation](https://www.tallievents.com/docs/languages) - [Registration form](https://www.tallievents.com/docs/registration-form) #### Team - [Team and roles](https://www.tallievents.com/docs/team-and-roles) - [Roles and activity log](https://www.tallievents.com/docs/roles-and-activity) #### Registration and attendees - [Public registration and tickets](https://www.tallievents.com/docs/registration) - [Attendees](https://www.tallievents.com/docs/attendees) - [Orders and group registration](https://www.tallievents.com/docs/orders-and-groups) - [Session sign-up and CE credits](https://www.tallievents.com/docs/sessions-and-credits) #### Communication - [Emails and contact lists](https://www.tallievents.com/docs/emails) - [Surveys](https://www.tallievents.com/docs/surveys) #### Planning and websites - [Tasks and checklists](https://www.tallievents.com/docs/tasks-and-checklists) - [Event website](https://www.tallievents.com/docs/event-website) #### Exhibitors - [Exhibitors](https://www.tallievents.com/docs/exhibitors) - [Brand portal and booth scanner](https://www.tallievents.com/docs/brand-portal) #### At the door - [Check-in](https://www.tallievents.com/docs/check-in) - [Devices and offline check-in](https://www.tallievents.com/docs/devices-and-offline) - [Talli for iPhone](https://www.tallievents.com/docs/mobile-app) #### Reports and AI - [Dashboard, overview and reports](https://www.tallievents.com/docs/dashboard-and-reports) - [AI assistants](https://www.tallievents.com/docs/ai-assistants) [Docs](https://www.tallievents.com/docs) / Events # Write with AI Write with AI drafts your event's copy from a few words about what it should say, in the tone and reading level you choose. Dates, times, the venue and the number of seats always come from the event itself, and nothing is saved until you keep it. ## Draft an event description Owners and admins: 1. Open the event for editing: choose **Edit** next to it in **Events**. 2. Under **Description**, choose **Write with AI**. 3. In **What should this say?**, write who the event is for and what to cover, for example "A morning for small employers on keeping crews safe in summer heat. Friendly and practical." You do not need to type the date, time or venue: Talli adds them from the event. 4. Pick a **Tone**: **Warm** (the default), **Plain** or **Formal**. 5. Pick a **Reading level**: **General** (the default), **Simple** (short sentences and common words) or **Professional**. 6. Choose **Write draft**. The draft appears under the request, marked **AI draft**. It is written in the event's language. To try again with different words, tone or reading level, change them and choose **Write again**: it redrafts every part you have not kept yet. ![The Write with AI panel beside an event: a short prompt, tone and reading level choices, what Talli already knows, and a drafted description with Keep, Rewrite, Edit and Discard.](https://www.tallievents.com/api/media/1aa3f0cc-1c6d-49d2-87d7-822f9a19e1b8/talli-write-with-ai-panel.webp) Write with AI drafting a description. Shown with sample data. Ask your assistant ``` Draft a description for the Spring Safety Seminar in a warm, plain tone for small employers. Show me any warnings before I keep it. ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `draft_copy`, `update_event`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## Draft the registration welcome text The welcome text is the few sentences above the form on the registration page. 1. Open the event, choose **Registration** in the sidebar, and stay on the **Form** tab. 2. In the **Welcome text** card, choose **Write with AI**. 3. Write what it should say, pick a tone and reading level, and choose **Write draft**, as for a description. Keeping the draft saves it as the welcome text right away, and the card shows it. Ask your assistant ``` Write a short welcome text for the registration page of the Spring Safety Seminar, in the same tone as its description. ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `draft_copy`, `update_event`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## Keep, edit or discard a draft A draft has one part for each text it writes: the description, or the welcome text. Each part has these buttons: - **Keep** saves the text right away, exactly as shown (to the description or the welcome text), and marks the part **Kept**. The field on the page shows the kept text too. - **Rewrite** redrafts just this part with the current request, tone and reading level, even after you kept it. - **Edit** opens the text so you can change it; choose **Done** to see it again as it will read. An edited part is marked **Edited**, and you can keep it like any other. - **Discard** sets the part aside; **Restore** brings it back. Where a draft has more than one part, **Keep all** at the bottom of the panel keeps every part not yet kept or discarded, in one save. It stays off while any of those parts has a warning. Closing the panel saves nothing. After you keep a part, you can still edit the field on the page as usual and save it. ## Check the facts in a draft Talli writes the event's title, date, time, venue name, venue address and capacity into every draft from the event itself, so they are always right. Talli then checks the draft for any date, clock time, money amount or number of two or more digits that is not one of the event's own details. - Each one is highlighted in the text and listed in a warning, for example: "March 3" is not in the event's details. - **Keep** stays off for that part while any warning is left. Choose **Edit**, change or remove the highlighted words, and **Keep** turns on once the check finds nothing. If a flagged detail is right but not part of the event (a lunch price, for example), keep the rest and add that detail in the field on the page yourself. - While you edit, the warnings update as you type. - Screen readers hear how many things there are to check once, when the draft arrives. - Talli checks again when you keep a part, so text with a warning is never saved from the panel. - A part with nothing to check says "Every date, time and number matches the event." The check applies to text kept from the Write with AI panel. Text you type into the description or welcome text field yourself and save with the page's own Save button is yours, and is saved as you wrote it. The event's facts written another way still match: for an event on Tuesday, June 22, 2027 at 9:00 AM, "June 22", "9 AM" and "2027" are not flagged. Numbers from the venue's address (the street number and ZIP code) and the capacity are never flagged either, so "Up to 120 may join" is fine for a 120-seat event. Dates are checked in English and in the event's own language: for a Spanish event, "3 de marzo" is flagged, and for a Chinese event, "3月3日" is. Ask your assistant ``` Check this text against the details of the Spring Safety Seminar and tell me anything that does not match: [paste your text] ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `check_copy`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## What the AI knows about the event - The event's title. - Its date and time, written in the event's time zone and language (for example "Tuesday, June 22, 2027" and "9:00 AM - 1:00 PM EDT", or "martes, 22 de junio de 2027" and "9:00 - 13:00 GMT-4" for a Spanish event). - The venue's name and address. - The capacity. - The attendee types, for example Employer or Broker. It does not see registrations, attendees or anything outside the event. ## Who can use it Owners and admins can write with AI, because keeping a part changes the event. Staff cannot open an event's edit page, and see the welcome text without the Write with AI button. ## Limits and edge cases - A request can be up to 2,000 characters. - Drafts are plain text: no formatting, links or HTML. Anything that looks like HTML in a draft is shown and saved as ordinary text. - The fact check reads written dates in English and in the event's language, in the forms that language writes them. Numeric dates are read month first in English (3/14 is March 14); in other languages only the full numeric form with a year (for example 13/3/2027 in Spanish) is read as a date, and a shorter one is checked as numbers. A single-digit number on its own (for example "3 sessions") is not checked. - The welcome text can be up to 1,000 characters. - Kept text is the event's source text: Talli translates it into the event's other languages automatically, like any description you type; see [Languages and translation](https://www.tallievents.com/docs/languages). - If the writer cannot produce a draft, Talli says so in the panel and nothing changes. Try again, or reword the request. ## Coming soon - Write with AI for emails and exhibitor booth pages. It already writes [event website](https://www.tallievents.com/docs/event-website#write-the-text-with-ai) sections. - Using agenda sessions in drafts. ## From an AI assistant - `draft_copy` with `{ eventId, purpose, prompt, tone?, readingLevel?, language?, parts? }` (owners and admins) returns `{ parts: [{ key, text, warnings }], facts }` and saves nothing. `purpose` is `event_description`, `registration_intro`, `email_body`, `website_section` or `booth_page`. `tone` is `warm` (default), `plain` or `formal`; `readingLevel` is `general` (default), `simple` or `professional`; `language` is a BCP 47 tag and defaults to the event's language. `parts` defaults by purpose: `["description"]`, `["intro"]`, `["subject", "body"]` for `email_body`, and `["heading", "body"]` for `website_section` and `booth_page`. Each warning names one date, time, amount or number that is not in the event's details. - `check_copy` with `{ eventId, texts }` (owners and admins) returns `{ findings }`: for each text, the dates, times, amounts and numbers that are not in the event's details; an empty list means nothing to check. - `draft_copy` and `check_copy` work on read-only connections, because they change nothing. - To keep a description, the assistant checks the warnings with the person and calls `update_event` with `{ eventId, description }`; for the welcome text (`purpose: "registration_intro"`, part `intro`), `update_event` with `{ eventId, registrationIntro }`. [Back to all guides](https://www.tallievents.com/docs)