Theater CRM
In a theater, revenue comes from three separate places: the single-ticket theatergoer, the season subscriber, and the school or company that takes the whole house. When the subscription renewal period and group requests from touring cities fall in the same week, a breakdown shows up anywhere the lists are kept apart.
The subscription end date is a field on the person record; a group booking moves through request, hold, deposit and confirmed stages, and expired holds show on the list.
- Keep the season subscription's end date as a field and call subscribers entering the renewal period from a single list
- Run school and company group bookings through request, hold, deposit and confirmed stages
- Build up on each theatergoer's record which play they saw and when, and split the new production announcement by that history
- Track venue conversations in tour cities, technical requirements and the revenue-share terms on a single record
| Season Subscription | A subscription is a record linked to the person record; the package, the start date and the end date are in fields, and those nearing their end drop into the renewal list. |
|---|---|
| Group Seat Hold | A school or company request is a record with request, hold, deposit and confirmed stages; the seat count, the performance date and the deposit status are in its fields, and blocked seats whose hold period has expired appear on the list. |
| Audience History | Every play seen is a line under the person record; the announcement list is filtered on the genre and the date in that history. |
| Tour and Venue | The tour city and the venue are each a field; the technical requirements and the revenue-share terms sit on the same record and are compared with the previous season. |
In theater, the relationship with the audience does not squeeze into a single box-office transaction. A season subscriber remembers which plays they saw last year and expects the renewal call to reflect that; a school asks for a matinee for two hundred students, and the teacher's name, the coach time and the deposit payment are all discussed inside the same conversation; a sponsoring company takes the whole house for a private performance. The box-office system does not hold these three relationships, because the box office counts tickets. And when the company goes on tour, what was discussed with the venue manager in that city, the technical requirements and the revenue-share terms all stay in one person's inbox.
In Rapitek CRM the theatergoer is a person record and the school or company is an account record; which play they saw and when builds up under that record. Because the subscription end date is a field, subscribers entering the renewal period drop into a list and the call turns into a task. A group booking is a record with its own stages: request, hold, deposit and confirmed are separate steps; the seat count and the performance date sit in fields, and those whose hold period has expired appear on a separate list. The tour city and the venue are fields too, and the terms agreed with that venue stay on the same record. The announcement of a new production goes out from the same system over SMS and WhatsApp; who received which message leaves a trace on the card.
The scope of the plans and the separately priced items are written on the pricing page.
