KENYA · GUIDE 0577 · EDITION 4.2
Conference registration support in Kenya: Customers and Market Demand
The buyer and the buying decision
Training providers and conference organizers. The offer to test is: Manage attendee registration and check-in records for a defined event.
Administer conference registrations from an approved attendee list, agreeing ticket categories, delegate details, substitutions, payment authority, confirmation routing, and the separation between registration completion and the organizer's own attendance, refund, or admission decisions under the actual published event terms supplied to delegates before booking.
Separate interest from an accepted order
Test a small registration form and check-in workflow with fictional attendees.
The purpose of this test is to establish whether the buyer accepts the specified result, delivery arrangement and payment terms. An encouraging interview does not establish repeat demand. Ask what the buyer currently uses, what would make them change supplier and who has authority to approve the first order. Record a refusal as carefully as an enquiry so that unsuccessful offers do not disappear from the evidence.
Collect evidence specific to this offer
Record attendee approvals, registration categories, organizer references, payment status supplied by the client, confirmation delivery, substitution requests, unresolved form errors, and final delegate reconciliation so the business can distinguish prepared submissions from registrations genuinely confirmed by the conference organizer under the selected booking category.
| Question to resolve | Evidence to retain |
|---|---|
| What exactly will the buyer accept? | Ask the client to reconcile registered delegates with organizer confirmations, checking spelling, session selections, duplicate entries, dietary information handling where necessary, and substitutions that require the organizer's approval rather than simply changing a name in an internal attendee spreadsheet after the original ticket was issued. |
| What is included in the first trial? | Administer conference registrations from an approved attendee list, agreeing ticket categories, delegate details, substitutions, payment authority, confirmation routing, and the separation between registration completion and the organizer's own attendance, refund, or admission decisions under the actual published event terms supplied to delegates before booking. |
| How will a prospect see the offer? | Offer organizers a practical pilot before committing to a full event. |
| What must happen before repeating the trial? | Attendee counts reconcile and personal data is not exposed on public lists. |
Decide whether to continue
Review the specification with the buyer before committing to tools or stock. A trial is commercially useful only if actual costs, rejected work, time spent and cash collected can be reconciled. A registration appears complete internally while the delegate remains unregistered if payment did not match the organizer's reference or confirmation went to an unattended address, leaving the traveller without the practical evidence required when arriving at the conference's actual registration desk on the event day.
If a buyer changes the required output, record a new scope and re-cost the test. Do not count a request for a different product as proof of demand for the original one. Keep personal contact details in your private records and use customer statements publicly only with permission.
Turn the example into a buyer test
Fictional registration REG-77 prepares a fifty-person conference roster, fifty name badges and a check-in register for one morning event. Sample row: attendeeA017, approved badge name, organisation if permitted, ticket category, registration status and arrival status. Payment verification remains with the organiser. Accessibility/dietary requests are routed privately to authorised staff, not printed on badges. The service excludes ticket sales, payment handling, security screening and guaranteeing attendance. Any live invitations or reminders require separate explicit sending authority.
| Buyer discussion | Evidence to retain |
|---|---|
| Specification to confirm | A form submission or payment screenshot is not automatically a confirmed ticket. |
| Output to inspect | Fifty registrations do not imply fifty arrivals; organiser receives unresolved cases without private data in public reports. |
| Failure that can defeat acceptance | Attendee appears twice |
Ask the buyer to describe one acceptable and one unacceptable result. Record the decision maker, price basis, quantity, handover point and payment date privately. A sample request, an encouraging conversation and an accepted order are different evidence. Keep the first commitment within your demonstrated capacity; no customer interview or successful trial is asserted here.
What a failed test should change
Compare unique reference and actual registration evidence.. If the offer cannot meet that check, revise the specification or process before promising a repeat. Keep rejected offers and reasons in the same register as positive replies so that your record does not exaggerate demand.