Frequently Asked Questions

The workflow starts with an organization, then an event, candidates, campaigns, public candidate experiences, voting or engagement, verification, and rankings or results. Teams can prepare these pieces before launching a live campaign.

Yes. The approved MVP allows an event to have one or more voting campaigns. Campaign configuration and launch remain separate from the event record.

No. Publishing an event makes the event available according to its configured visibility, but it does not automatically launch a voting campaign. Event publication and campaign activation are separate lifecycle decisions.

A campaign is a configured participation or voting activity connected to an event. It has its own lifecycle and may be prepared in draft before an organization decides to launch it.

No. An event is the pageant edition. A campaign is an activity connected to that event, such as a voting campaign. Keeping them separate lets teams prepare event content without automatically launching voting.

Supporters visit the public campaign experience, select a candidate, and complete the available voting flow. Paid-vote fulfillment follows successful payment verification; starting checkout alone does not credit votes.

Rankings can support organizer-facing review of campaign activity, while leaderboards are typically the public-facing presentation of standings where enabled. The exact visibility depends on the configured experience.

Rankings and leaderboards describe campaign activity and verified results where supported. They should not be read as a promise of judge scoring or official tabulation unless that capability is separately approved and configured.

A Candidate is the reusable person identity associated with a pageant participant. Their participation in a particular event is represented by an event-specific profile and context.

Yes. The Candidate identity can be reused across events, while each event can hold its own participation details and profile context.

Yes. Event-specific participation can carry context that belongs to that pageant edition, while the reusable candidate identity remains distinct from the event profile.

A candidate microsite is a public profile and campaign destination for a candidate in an event. It can present approved candidate information and provide the public experience connected to that event.

Yes. A public candidate page is connected to the candidate’s participation in a particular event, so the event context and campaign experience remain clear to visitors.

Yes. The public voting experience is designed to let supporters select a candidate within an active campaign and follow the available voting flow.

PageantXero currently uses guided Early Access. Request a demo first, then use the discovery and demo process to determine the right next step and receive manual or backend activation where appropriate.

PageantXero is currently offered through guided Early Access. Availability, activation, and the right setup path are discussed through the demo and discovery process.

The demo gives your team a chance to discuss the organization, event, candidate, campaign, and public-experience workflow before activation. It also keeps the current Early Access process guided rather than implying open self-service registration.

The current path is Request a Demo, followed by a discovery and demo call. If the fit and timing are right, PageantXero can then be activated manually or through the backend for Early Access.

Requesting a demo is an invitation to discuss PageantXero with the team. For current commercial details, including any applicable plan or campaign charges, refer to the canonical Pricing page rather than this reusable FAQ.

See the canonical Pricing page or discuss your needs during a demo. Pricing, billing, and commercial rules can change, so this FAQ does not duplicate detailed rates, fees, tax, settlement, or revenue-share terms.

Yes. One organization may manage multiple pageant events, such as different editions, titles, or seasons, while keeping the organization as the parent context.

Yes. Organization branding is intended to be reusable across events. An event may also have its own event-level visual identity where that capability is supported; this answer does not imply full white-label or custom-domain support.

An event holds its pageant edition details, dates, status, candidate participation, public presentation, and connected voting campaigns. It is the specific edition that an organization is preparing or running.

Yes. The approved MVP allows an event to have one or more voting campaigns. Campaign configuration and launch remain separate from the event record.

No. Publishing an event makes the event available according to its configured visibility, but it does not automatically launch a voting campaign. Event publication and campaign activation are separate lifecycle decisions.

A Candidate is the reusable person identity associated with a pageant participant. Their participation in a particular event is represented by an event-specific profile and context.

Yes. The Candidate identity can be reused across events, while each event can hold its own participation details and profile context.

Yes. Event-specific participation can carry context that belongs to that pageant edition, while the reusable candidate identity remains distinct from the event profile.

Yes. A public candidate page is connected to the candidate’s participation in a particular event, so the event context and campaign experience remain clear to visitors.

No. An event is the pageant edition. A campaign is an activity connected to that event, such as a voting campaign. Keeping them separate lets teams prepare event content without automatically launching voting.

Yes. QR codes can be placed on posters and other event materials to help supporters reach the relevant public candidate or event experience.

PageantXero is connected pageant technology for organizations that need to manage events, candidates, campaigns, public candidate experiences, voting, and results in one workflow.

PageantXero is designed for pageant directors, franchise holders, event organizers, committee leads, staff, candidates, and public supporters. Each role can participate in the parts of the experience relevant to them.

An organization can prepare and run events, manage candidate records and assets, create candidate microsites, configure campaigns, share QR destinations, and review rankings or verified results where supported.

No. Online voting is one part of the product. PageantXero connects organization setup, event management, candidate visibility, campaigns, public experiences, payment verification, and rankings so teams can manage the lifecycle around a pageant.

The workflow starts with an organization, then an event, candidates, campaigns, public candidate experiences, voting or engagement, verification, and rankings or results. Teams can prepare these pieces before launching a live campaign.

PageantXero currently uses guided Early Access. Request a demo first, then use the discovery and demo process to determine the right next step and receive manual or backend activation where appropriate.

PageantXero is currently offered through guided Early Access. Availability, activation, and the right setup path are discussed through the demo and discovery process.

PageantXero is connected pageant technology for organizations that need to manage events, candidates, campaigns, public candidate experiences, voting, and results in one workflow.

PageantXero is designed for pageant directors, franchise holders, event organizers, committee leads, staff, candidates, and public supporters. Each role can participate in the parts of the experience relevant to them.

An organization can prepare and run events, manage candidate records and assets, create candidate microsites, configure campaigns, share QR destinations, and review rankings or verified results where supported.

The workflow starts with an organization, then an event, candidates, campaigns, public candidate experiences, voting or engagement, verification, and rankings or results. Teams can prepare these pieces before launching a live campaign.

PageantXero currently uses guided Early Access. Request a demo first, then use the discovery and demo process to determine the right next step and receive manual or backend activation where appropriate.

An event holds its pageant edition details, dates, status, candidate participation, public presentation, and connected voting campaigns. It is the specific edition that an organization is preparing or running.

The demo gives your team a chance to discuss the organization, event, candidate, campaign, and public-experience workflow before activation. It also keeps the current Early Access process guided rather than implying open self-service registration.

The current path is Request a Demo, followed by a discovery and demo call. If the fit and timing are right, PageantXero can then be activated manually or through the backend for Early Access.

A candidate microsite is a public profile and campaign destination for a candidate in an event. It can present approved candidate information and provide the public experience connected to that event.

Yes. A public candidate page is connected to the candidate’s participation in a particular event, so the event context and campaign experience remain clear to visitors.

No. A QR code opens a public candidate or event experience. Visitors still need to review the experience and complete the available voting flow; a scan is not itself a vote or a payment.

A candidate QR code opens the candidate’s public event-specific experience, such as a microsite or voting destination. It is a convenient way to connect printed materials with the public page.

An Organization represents the pageant brand or team that owns and manages one or more events. It is the level where core organization details and reusable brand information are maintained.

Yes. Organization branding is intended to be reusable across events. An event may also have its own event-level visual identity where that capability is supported; this answer does not imply full white-label or custom-domain support.

An organization can prepare and run events, manage candidate records and assets, create candidate microsites, configure campaigns, share QR destinations, and review rankings or verified results where supported.

An Organization represents the pageant brand or team that owns and manages one or more events. It is the level where core organization details and reusable brand information are maintained.

Yes. One organization may manage multiple pageant events, such as different editions, titles, or seasons, while keeping the organization as the parent context.

Yes. Organization branding is intended to be reusable across events. An event may also have its own event-level visual identity where that capability is supported; this answer does not imply full white-label or custom-domain support.

Supporters visit the public campaign experience, select a candidate, and complete the available voting flow. Paid-vote fulfillment follows successful payment verification; starting checkout alone does not credit votes.

Paid votes are eligible for fulfillment after the payment is verified as successful. A checkout attempt or an unsuccessful payment should not be treated as credited votes.

No. A QR code opens a public candidate or event experience. Visitors still need to review the experience and complete the available voting flow; a scan is not itself a vote or a payment.

Payment and voting are connected through the campaign’s fulfillment flow, but they are not the same lifecycle. A payment must be verified successfully before eligible paid votes are credited.

An unsuccessful payment is not a verified successful payment, so it should not be treated as credited paid votes. The transaction state remains distinct from campaign and voting state.

Requesting a demo is an invitation to discuss PageantXero with the team. For current commercial details, including any applicable plan or campaign charges, refer to the canonical Pricing page rather than this reusable FAQ.

See the canonical Pricing page or discuss your needs during a demo. Pricing, billing, and commercial rules can change, so this FAQ does not duplicate detailed rates, fees, tax, settlement, or revenue-share terms.

No. A QR code opens a public candidate or event experience. Visitors still need to review the experience and complete the available voting flow; a scan is not itself a vote or a payment.

A candidate QR code opens the candidate’s public event-specific experience, such as a microsite or voting destination. It is a convenient way to connect printed materials with the public page.

Yes. QR codes can be placed on posters and other event materials to help supporters reach the relevant public candidate or event experience.

Rankings can support organizer-facing review of campaign activity, while leaderboards are typically the public-facing presentation of standings where enabled. The exact visibility depends on the configured experience.

Rankings and leaderboards describe campaign activity and verified results where supported. They should not be read as a promise of judge scoring or official tabulation unless that capability is separately approved and configured.

Supporters visit the public campaign experience, select a candidate, and complete the available voting flow. Paid-vote fulfillment follows successful payment verification; starting checkout alone does not credit votes.

Paid votes are eligible for fulfillment after the payment is verified as successful. A checkout attempt or an unsuccessful payment should not be treated as credited votes.

Payment and voting are connected through the campaign’s fulfillment flow, but they are not the same lifecycle. A payment must be verified successfully before eligible paid votes are credited.

An unsuccessful payment is not a verified successful payment, so it should not be treated as credited paid votes. The transaction state remains distinct from campaign and voting state.

No. Online voting is one part of the product. PageantXero connects organization setup, event management, candidate visibility, campaigns, public experiences, payment verification, and rankings so teams can manage the lifecycle around a pageant.

No. Publishing an event makes the event available according to its configured visibility, but it does not automatically launch a voting campaign. Event publication and campaign activation are separate lifecycle decisions.

A campaign is a configured participation or voting activity connected to an event. It has its own lifecycle and may be prepared in draft before an organization decides to launch it.

Supporters visit the public campaign experience, select a candidate, and complete the available voting flow. Paid-vote fulfillment follows successful payment verification; starting checkout alone does not credit votes.

Yes. The public voting experience is designed to let supporters select a candidate within an active campaign and follow the available voting flow.

Paid votes are eligible for fulfillment after the payment is verified as successful. A checkout attempt or an unsuccessful payment should not be treated as credited votes.

No. A QR code opens a public candidate or event experience. Visitors still need to review the experience and complete the available voting flow; a scan is not itself a vote or a payment.

Payment and voting are connected through the campaign’s fulfillment flow, but they are not the same lifecycle. A payment must be verified successfully before eligible paid votes are credited.

An unsuccessful payment is not a verified successful payment, so it should not be treated as credited paid votes. The transaction state remains distinct from campaign and voting state.