To set up an agency app that serves many clients, build one agency-branded app, create each client occasion inside it with its own look and sections, issue join codes or QR cards per occasion, give roles per occasion and route support requests to your team. Guests install once and join each occasion.
Who this is for
You are an event agency or planner who runs weddings, conferences, offsites and reunions for many clients. Today you build or rent an app per event, or you rely on WhatsApp groups and PDF itineraries. Each build costs setup time, store submission and a new learning curve for guests. You want an asset that you reuse.
A multi-occasion app is that asset. It is not a magic switch: it needs a structure, a naming scheme and a routine. This guide walks through one.
Step 1: decide what the app’s identity is
The app carries your agency’s name and look. Each occasion inside it can have its own colours, section names and bottom-bar shortcuts, so a wedding feels like a wedding and a corporate offsite feels like a corporate offsite. Decide what stays constant (your logo, the way guests join, the support route) and what changes per client.
Android holds 93.89% of India’s mobile OS market (StatCounter, 2026), so check your icon and splash on Android first, on a plain mid-range handset.
Step 2: define the occasion template
Write down what a typical occasion contains: timeline, reels, gallery, one-to-one connect, a discussion forum, a hospitality tile for room, travel and pickup, and a support request desk. Then decide which modules are on by default and which are added per client. A template speeds each new occasion, because you only change what is different.
Keep the template short. It is easier to switch something on for a client than to explain why something is cluttering the app for everyone.
Step 3: name occasions consistently
Agree a naming scheme before you create the first occasion: client, event, year. “Mehta Wedding, Udaipur, 2027” is clearer than “Mehta”. A consistent scheme lets your team find an occasion at once, and stops two clients with the same surname getting confused.
Record, for each occasion, the client contact, the dates, the owner on your team, the join code and the status.
Step 4: issue join codes and QR cards
A guest installs the app once, then joins an occasion by typing a code or scanning a QR. Make the code short and memorable, and print the QR on the invitation, the welcome card or the first message. Occasions in the guest’s app list are limited to those they belong to or have joined by code, so one client’s guests never see another’s events.
Test the join flow on a new phone before you send it to anyone. The first impression is the join.
Step 5: set roles per occasion
Owner and Manager roles apply to one occasion, not across the whole app. Give a client’s family member or HR lead Manager access for their own occasion, and keep Owner rights for your team. Roles appear on the Profile screen as extra buttons: attendance, triggers, live polls and support. Brief each Manager on what they can do and what they should not.
If a client wants to run their own notifications, give them the screen and a written rule on timing and audience.
Step 6: route support through the app
A support request desk turns scattered WhatsApp messages into a trail. A guest raises a request, picks a category, attaches photos or files and follows it through Open, In Progress, Resolved and Closed. A manager can assign a request to themselves. Define categories that fit your clients: travel, stay, food, schedule, other.
Set a response time you can keep, for example thirty minutes during the event. Tell guests where to find the desk.
Step 7: run each occasion with a routine
Use the same checklist each time: confirm guest list, import members with groups, set the look, publish the agenda and hospitality pages, test join and login, brief Managers, rehearse, launch, run, export, close. The routine is what turns the app from a gadget into a service.
Keep a log of what each client asked for and what you learnt. After five occasions, you will know which modules clients want and which they ignore.
Step 8: close and hand over
After the occasion, export the records the client needs, such as attendance and hospitality, and archive the occasion. Decide what happens to the guests’ photos and the gallery, and how long they remain available. Ask the client for feedback and for permission to use their occasion as a reference, at a level they are comfortable with: unnamed, named or with logo.
Common mistakes
Letting every client choose every module. The app becomes slow to configure and harder to support. Offer a menu, not a blank page.
Reusing a join code. Treat each code as belonging to one occasion and retire it afterwards.
Mixing client data. Keep one list per occasion and never copy rows across clients.
Skipping the store-submission buffer. Sociana submits each branded app; plan the first launch early.
A sample onboarding sheet for each new client
Capture the same ten items every time: client name and contact; occasion name and dates; owner on your team; number of guests and groups; login method; modules switched on; look and colours; join code and QR; Manager names; and the date the occasion archives. Put it in a shared sheet with one row per occasion. The sheet tells a new team member in two minutes what is live, who is responsible and which codes are in use. It also gives you the data to price and plan the next client: how long setup took, which modules were requested and what the client asked for in the first week.
How Sociana handles this
Multi-event and agency apps support a multi-occasion app with a list and search, join by code or QR, per-occasion branding and roles per occasion. Occasion and attendee codes handle joining, the admin panel and roles keep templates and per-occasion configuration, help desk and support requests route guest requests, and groups separate cohorts within an occasion.
Occasion Xperts is an events agency that runs weddings, conferences, offsites and reunions from a single branded Sociana app, with Explore Occasions, Join with Code, per-occasion branding, a Support Request desk and roles Owner, Manager, Guest and Visitor. Its recorded lessons: an agency gets more from one durable app than from a new store listing per client, and a ticket trail per occasion replaces scattered WhatsApp requests. Read the Occasion Xperts case study.
Frequently asked questions
Can each client have its own colours?
Yes. Each occasion keeps its own branding, section names and shortcuts inside the same app.
Will clients see each other’s events?
No. A guest sees only the occasions they belong to or have joined by code.
Does a new client need a new store submission?
Not once the multi-occasion app is live; a new occasion is added inside it. Sociana still submits the agency app itself to the stores.
Who handles guest support?
Your team, through the Support Request desk, with Managers assigned per occasion. Agree response times with each client.
Related reading
Glossary: occasion code, occasion template, branded app, organisation. Occasion hubs: agency multi-client apps, weddings and cultural offsites. See templates and checklists for an occasion setup checklist.