Map the attendee and event context
Use stable source identifiers, event dates, sessions, participation format, request fields, and consent. Keep unrestricted event engagement data outside the accommodation case.
Operate fulfillment in Evencue
Assign clarification, record the human decision, build service requirements, coordinate providers, confirm the attendee plan, run readiness, and close the outcome.
Keep recovery manual
Document duplicate handling, failed rows, retries, mapping changes, and source corrections. The event team must be able to enter or update a request without the connector.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
Does Evencue replace Whova?
No. It is a focused accommodation fulfillment layer beside Whova.
Is the Whova integration live?
Connector availability must be verified for the deployment. Manual entry and CSV import are the dependable activation paths.
Should fulfillment details be written back?
Only if a defined purpose requires it. Prefer safe status, references, or requester instructions over copying private case content into a broader event system.