Tessitura TNEW, taken past its defaults.

TNEW's default map shows seats on a grid. Our maps draw the house around them: the walls, aisles and stairs, the stage, row letters and the cross aisle. Buyers can see where they'll actually sit before they pay.

Every venue starts from the plan it already has. Send us the seating chart as a PDF, an image or even a sketch, and we draw it in our own seat map builder, a tool we developed for TNEW. It lines up the walls, aisles and stage with TNEW's seats, and turns the result into a custom map that loads straight into TNEW. We've drawn them for Mirvish's four theatres, Drayton Entertainment's venues across Ontario and Proctors in Schenectady.

The pairs below are traced from the live maps, seat for seat, and redrawn in our colours: available seats in blue and dark grey for two price levels, sold seats in light grey. On the Mirvish maps, the sold seats are for illustration.

Each seat can show a photo taken from that part of the house: in a small card when a buyer hovers over it, in the ticket window next to the section, row and price when they click it, and full size with one more tap. Fewer surprises at the door, and fewer calls to the box office asking what a seat is like.

A theatre's layout changes from show to show: a thrust stage, a pit that becomes seats, a section held back. Each venue's map settings say which version of each section a show uses. At Mirvish they live in designEdit, so the theatre's own staff make the change; at Proctors they live in a settings file we look after.

• Targeted. A map can apply to every show in a venue, to a production season, or to individual performances.
• Section by section. Each section of the house uses TNEW's default or one of the custom versions.
• Previewed first. Staff can check a new map on the live ticket link before buyers see it.
• Seat photos, if you want them. We can customize the settings to hold the view for each section or block of seats, so the theatre swaps a photo itself and it goes live without a developer. Or we look after the photos as a service.
• An off switch. Custom maps can be turned off at any time, and TNEW goes straight back to its default map. A fail-safe, if one is ever needed in the middle of an on-sale.

Mirvish's TNEW calendar marks performances Limited availability, Selling fast or Sold out. TNEW doesn't come with these. Our own logic adds up Tessitura's seat counts across the house for each performance and picks the label, so buyers can see at a glance which dates to book first.

We pull performances from Tessitura's API into the theatre's website, so the marketing site and TNEW never disagree. On mirvish.com, What's On lists every performance as a calendar or a list, filtered by month, show or venue, with the same availability labels and a Buy tickets link straight into TNEW.

Tessitura's API and TNEW's own pages open up more than the website. We build the tools a theatre needs around TNEW:

• Custom dashboards. Sales and attendance from Tessitura's data, for the people who need the numbers without opening Tessitura.
• Front of house. Screens for the door and the box office: find an order by name or email, check a QR ticket, and sort out a problem without a trip back to Tessitura.
• Internal tools. Whatever the team does by hand today, built on Tessitura's API and shaped to how they work.
• Calendar files. Performances buyers can add to their phone's calendar.
• Richer marketing data. At Mirvish, we add extra detail from each TNEW page to the data layer for their Google tags, and turn useful steps in the sale into events, so their marketing team can follow a campaign all the way to the order.

These can be built from scratch; on designEdit, our own framework; or as a custom front end on designEdit. designEdit already has staff accounts, permissions and admin screens, so a dashboard or a box office tool can connect to Tessitura sooner, and sit alongside the theatre's website and map settings in one place.

The maps are serverless: a set of files on a CDN, so they load quickly and don't slow TNEW's own pages. We can host them for you, set them up in your own AWS account, or wherever you need them. The arrangement is the same either way, built from one blueprint and already running for other theatres, so a new theatre is set up quickly. With no servers, there's nothing for your team to run, patch or update.

• One line in TNEW. That's the whole change to TNEW for the maps: a single line in its template. The maps load from an address on your own ticketing domain, with its own certificate, so buyers only ever see your name.
• Nothing is written to Tessitura. The maps only read. They fetch their own files, send nothing back, and never write to Tessitura. If a file can't be reached, TNEW shows its default map and the sale carries on.
• Low running cost. A handful of small files on a CDN, so keeping the maps up costs a theatre very little each month.