Booth Studio

Text Data.

Write documents that fill themselves in from your records. Place a field where a value belongs, and the document always says what its record says.

What is Text Data?

Text Data is how a document written once stays correct for every client. Instead of typing a name, a date or a total - and retyping it for the next booking - you place a field where the value belongs. The field reads from the record the document is linked to, so the document always says what the record says.

You never see code. A field appears as a readable chip like Client first name or Event date, named in plain words, and it fills in with the real value when the document is previewed, published or opened by a client.

Example - what you write

Hi Client first name, thanks for choosing us for Event name at Venue on Event date. Your total is Total, with a deposit of Deposit due by Deposit due date.

What the client reads

Hi Sarah, thanks for choosing us for the Harper Wedding at The Grand Pavilion on Saturday, June 14 2026. Your total is $2,450.00, with a deposit of $500.00 due by May 1, 2026.

The same paragraph works for the next wedding, the next corporate booking, and the one after that - each document fills in from its own record, and a change to the record is reflected everywhere the field appears.

Inserting fields

Fields work anywhere text does - headings, paragraphs, buttons, labels. There are three ways to place one, and they all produce the same chip:

  1. Use the picker. In the document builder, click Insert Text Data under any text field. Fields are grouped by record and searchable - click one and it lands where your cursor is.
  2. Write it inline. Drop fields mid-sentence while you type a heading or paragraph. The field becomes a chip inside your writing and moves with the text around it.
  3. Copy from the reference. Every row on the field reference page has a copy button. Paste the copied field into any text field in the builder and it becomes a chip.

Previewing with Data Fill

A document raised against a record opens filled from it - a proposal made from a lead reads as that lead’s proposal straight away. What it fills from is named in Data Fill in the builder toolbar.

Switch it off there and every field shows its own name again, which is what you want while arranging a page. A template or a standalone document has no record to fill from, so it starts off.

You can also pick any other event, contact or lead, and the canvas fills every field with that record’s real values. The document’s own record is offered first, because that is what publishing would produce today - but previewing against another record is a useful what-if: designing a proposal against a real booking is how you find out the venue line wraps.

Preview follows it. Press the eye with a record chosen in Data Fill and every size - Desktop, Tablet, Mobile and the PDF - shows the page filled from that record, with a line at the top naming it. Download PDF - there or in the ••• menu - saves that filled file, named after the record. Finalizing still uses the document’s own record.

Data Fill is a preview only. It never changes the document or the record - switch it off and every chip shows its name again.

What can be filled in

Fields are grouped by the record they read from. A few examples from each group:

  • Client Text Data. The person this document is for, and the company they belong to. 11 fields, such as Client name, Client first name and Client last name.
  • Event Text Data. The occasion - name, date, venue and size. Reads the inquiry until it is booked, then the booking. 8 fields, such as Event name, Venue and Event city.
  • Lead Text Data. The inquiry itself. These stop resolving once it is booked - for anything about the occasion, use Event. 4 fields, such as Lead name, Lead venue and Lead event date.
  • Financial Text Data. Totals and deposits, read from the record rather than typed by hand. 10 fields, such as Total, Deposit and Paid.
  • Business Text Data. Your own business. These resolve even in a template, which has no record. 6 fields, such as Your business name, Your business email and Your business phone.

How fields behave

The rules Text Data follows, so you can rely on what a client will see:

  • Empty fields stay blank. A field with no value prints nothing - never “null” or an error. A middle dot (·), bullet (•), bar (|), en dash (–) or em dash written right beside it goes with it (a hyphen (-) stays, as words do), so “Alex Morgan · Client company” reads “Alex Morgan” for a client with no company. Words stay: to drop a label such as “Prepared for”, select the line or its column and set Visibility to “Only when a field has a value”.
  • Fields need a linked record. Client, Event, Lead and Financial fields fill in from the record the document is linked to. A document with no linked record leaves those blank - only your Business fields resolve everywhere.
  • Event fields work on a proposal. A proposal is written before there is an event, so on a lead-linked document the Event fields - name, date, venue, guest count, event type - read the inquiry. Nothing changes when the lead is won: the same fields carry on reading the booking. Use them in preference to the Lead fields, which stop resolving once the inquiry becomes a booking.
  • Templates keep their fields. In a template there is no client or event yet, so fields stay as named chips. They fill in when the template becomes a real document with a real record behind it.
  • Publishing locks the values in. When you publish, the live values are captured into the document at that moment. What the client received stays as they received it, even if the record changes later.
  • Money fields say what the booking says. Paid is the money received against the booking and Balance due is the total less that - the same figures the booking’s Financials tab shows, read from the same records. A deposit taken before anything was invoiced is already counted, so a document never asks a client for money they have sent.
  • Typed tokens work too. A field is stored as a token like {{contact.email}}. If you type one by hand - even with spaces inside the braces - it is understood exactly like a picked field.
  • Nothing fails silently. A field this build does not recognise is shown by name on the page rather than hidden, so a document never quietly loses information.