Task · Customize this event's pages

Send your wording out for review

Share your event wording for review and publish approved changes one at a time.

3 steps · About 4 minutes

Create a review link to share your event pages and emails with someone outside Tito. Their suggestions wait for your approval before they reach attendees.

Create a review link

1. Open Customize on the event

2. Open More actions at the top and select Share for review

3. Select Create a review link, or Create review links if your event has more than one language

   Copy the link with the button beside it and send it to your reviewer. Step by step under the link opens the review the way they see it. With Guest review on, anyone with the link can review without signing in. Turn it off to ask every reviewer to sign in. If you have more than one event language, there's a link for each language, and Language picks which one shows.

   To have a reviewer sign in without access to the rest of your account, invite them on Team with the Copy reviewer role. When they sign in to Tito, they see the reviews they can open.

   Existing links continue to work until you select Revoke beside the link. Revoking a link keeps its suggestions and comments.

   go.tito.io/acme/summer-fetes-summer-fete/admin/customize?tab=words&zoom=50

Review the wording

The reviewer chooses Sign in or Continue as guest. A guest enters a name and, optionally, a company. They then choose an audience and journey, followed by an available or fully booked version.

The link opens on a choice of two ways in. Step by step goes through one scenario a screen at a time, and is where reviewers change wording and leave notes. All flows shows every screen in every scenario at once, laid out as the journeys people take. Drag to move around, and pinch or scroll to zoom. When the wording changes while All flows is open, its screens update to show it.

Review copy above each screen opens it in step by step, and the back arrow there returns to All flows at the same screen. For someone signed in with access to the event, the arrow beside it has Open in the Customizer.

The payment step shows the page your buyers pay on. When they pay on your pages, it has a sample of the card form Stripe adds there, in Stripe's own words. Reviewers can't select the sample to suggest wording or leave a note. When they pay on Stripe's page, the step says so, because Stripe writes every word there.

When buyers have one way to pay, the step after the payment step shows the page somebody with an unpaid order pays from. It's also the page a payment link you send opens, and All flows shows it on a row of its own.

When the event takes bank transfers, each journey that sells paid tickets has a Pays by invoice journey too. It starts with the payment page offering bank transfer, the page where the buyer gives the details for their invoice and commits to paying, and the order page with the bank details to pay to. Those bank details are your own account’s when buyers pay into it, and sample details when Stripe gives each buyer their own. When Stripe’s bank transfers need buyers to sign in, these pages show a signed-in customer. The journey then shows the invoice email and the reminder, overdue and cancellation emails, with a Default payment terms version that follows the event’s own settings, and one for each set of payment terms. Each version shows only the emails those terms send, with their due dates and wording. An accepted change there goes to the payment terms’ own wording when they have their own for that line. Otherwise it goes to everyone’s wording.

When an event's bank transfer needs buyers to sign in, each journey that sells paid tickets has a Signs in to pay by bank transfer version. It goes from the event page through the sign-in page, the email check, the details a new customer gives and their account page. Those pages use your account's wording rather than the event's, so a suggestion on them can't be accepted from the review. Change their wording in the account's Customize instead.

When a journey offers quotes and some of your customers need their quotes approved, it has a Needs approval to buy version too. It follows a school whose quotes go to its board: the payment page saying invoices need approval, the quote sent for approval and waiting, the quote as the board’s approver sees it, recording a purchase order, and rejecting the quote, with the emails each of those sends. The customers in it are samples, never your own. An accepted change to one of those emails goes to the event’s wording, like a change to any of its pages.

When the event has pages with their own address, a Pages scenario shows each page in the order of your Content list, with its title above it. On the scenarios page, each page has its own row. Pages whose address is switched off are included and marked as not published. Reviewers can suggest wording and leave comments on a page. When you accept a suggestion on a page’s title or words, the page changes in the review’s language. Suggestions on a Content block placed on another screen work the same way. A suggestion can’t be accepted from Review changes when its words appear more than once on the page, or when the page has no wording of its own in the review’s language. Change the page in Content, then reject the suggestion.

The first time a reviewer opens the link, a short walkthrough explains how the review works. They can open it again from How this review works on the scenarios page.

The review shows one screen at a time, including the emails that apply to the selected journey. Each email shows who it’s from, who it’s to and its subject. Opening an email preview doesn’t send an email.

If you’ve written a welcome message, it appears at the top of the scenarios page. A note you’ve written about a scenario appears under its name.

The event preview steps through the same date, time and ticket picker as the event page, one step at a time, so you can review the wording on each. When an event gives free tickets for buying others, the journey has a Free ticket offer step after the tickets are chosen.

When the main event page is closed, its purchase journeys are left out of copy review. You can still review audience journeys.

Click text to edit it, then select Save suggestion. You can leave a comment on any element with Add note. Cmd+Enter or Ctrl+Enter saves the focused form. Suggestions stay in review until you publish them.

Review together

You can see other reviewers’ comments and replies on each element.

Comment icons and counts appear beside elements with comments. A pencil appears beside elements with suggestions. Select an icon to open that element’s review panel.

You can delete your own comments and replies with Delete. Approvers can delete anyone’s, from the review or from Review changes. If a deleted comment already has replies, the replies stay under a note that the comment was deleted.

Type @ while writing a comment or reply, then choose another reviewer from the list. The list includes people who have joined the review and team members who have set their name in Edit profile. Team members and signed-in reviewers receive mention emails that link to the conversation. Guests can comment, reply and be mentioned, but they must sign in to receive mention emails. A plain reply doesn’t notify everyone.

Approve changes

A signed-in approver selects Review changes in the review toolbar. This opens Review changes, with a sidebar that keeps suggestions and comments across screens and languages.

Use Pending for open items and History for earlier decisions. Each item in History is labeled with what happened to it: Accepted, Rejected, Resolved or Replaced.

Select a suggestion to preview it. Edit Wording to publish when you want to publish it, then select Accept change. This publishes only that wording for the event and language wherever it appears.

When a suggestion changes only a few words, What changed shows the suggestion once with the removed words struck through and the added words underlined.

On an audience's journey, an accepted change goes to that audience's own wording when it has its own for that line. Otherwise it goes to everyone's wording.

Select Notify these reviewers to email the people involved in a decision. The people who will be emailed are listed under the checkbox, and only people who have signed in can be emailed.

• With Accept change, it emails the reviewer who made the suggestion.
• With Resolve comment, it emails the person who wrote the comment and everyone mentioned in it or in its replies.

The checkbox remembers what you chose last time.

Accept all changes publishes every pending suggestion, in every language, as it was written. It asks you to confirm first, and the confirmation has the same checkbox. Comments aren’t resolved.

Other draft content stays in draft. Select Reject suggestion to reject a suggestion. Select Resolve comment to resolve a comment. You can select Reopen for a rejected or resolved item.

Select Reviewer notes to write a welcome message for the scenarios page, and to give each scenario a name and a note on what it covers. There’s one welcome message for the event, and reviewers in every language see it. Untick Show to reviewers on a scenario to leave it out of the review for every reviewer.

Every element comment has a conversation. Select Reply to open the thread's reply box, then select Send. The reviewer and approver can both continue the conversation. A reply reopens a resolved thread in Pending. Replies do not publish or reject suggestions. Conversations refresh while the page is open, but refresh pauses while you’re writing to preserve unsaved suggestions and comments.

History keeps earlier wording versions and the details of who published each one. Keep placeholders such as {event} in email wording. A suggestion whose original wording can’t be matched is still readable, but can’t be published directly.

Suggestions and comments stay in Review changes when you delete an audience or switch off a way to register. Each one names the scenario and screen it was left on, and a comment shows the wording it was about. You can still reply to them, resolve them and reject them. A suggestion on a scenario that’s left the review can’t be accepted there, so change the wording in Customize, then reject the suggestion.

Every comment, reply and suggestion shows the date and time it was written.

You can also edit your wording in a spreadsheet.