How does it work?

The Free tier

The Free tier is enough to run a series of webinars or a smaller conference, non-commercial use included, for education, say, or to support and grow leisure activities.

A business organizer can use the Free tier instead of a demo, to try out what Amphi can do. Apart from one exception (uploading a video file), the Free tier is not cut down on features; only the quotas limit how far it takes you.

The licensing model also supports preparing an event on the Free tier for real from the start. As soon as prospective attendees begin registering, interest grows and you approach the quota ceiling, you can upgrade to a higher plan at any time. All the work you have done is kept.

The Premium tier

The Premium tier is aimed at the commercial sphere: at those who use Amphi as a sales channel, to build awareness of their brand, or for their own event-organizing business. The main difference from the Free tier is not the feature set but the quotas; Premium raises them across all functionality.

It is the higher quotas that let you make full use of regular, bulk communication with your audience: invitations, reminders and feedback collection. Amphi also helps you collect marketing consents from attendees right at registration; see GDPR and marketing consents.

Another big advantage is that the address of the public page can run on your company domain: conference.yourcompany.com. Setting it up is genuinely simple and we will help you; see Branding.

Technical support from the development team and a key account manager are available to you, both during setup and while the event runs.

The Enterprise model

Enterprise is a bespoke solution. You reach for it when you need an original site for your conference, integrations with your own systems, or features the standard plans do not cover.

We offer the full service, from analysis and design through to development. We do not run production services ourselves, but we will put you in touch with one of our partners. Both the scope and the price follow what you actually need; see Individual items (Enterprise).

Enterprise is agreed in a separate contract. The terms of the cooperation therefore differ from the standard terms and conditions.

Contact us

This choice cannot be changed later. Every event starts on the Free plan though, so you can try everything out first and upgrade to a paid plan only once you are sure.

Webinar

The license runs for one month from the payment date. For details see License payments – schemes. Attendee registration, email sending and every other feature need an active license; once it expires, the whole event moves to archive mode.

Conference

No more than 30 calendar days may pass between the first and the last talk day. The date of the first talk day is set when you create a new Event.

After the 30-day talk window the conference space stays active for a further 365 days. During that time you can keep communicating with attendees through Amphi. Only then does the Event move to archive mode. That comes with certain limitations.

There is no limit on how long you use Amphi before the first talk day. You can start preparing the conference well in advance and add content gradually, have speakers fill in their profiles, or invite attendees; see Attendee and speaker registration.

Licensing

• One event needs one license.
• The discounted annual bundle of up to 50 licenses is available for Premium Conference only; it cannot be offered for Premium Webinar. See the pricing page.

Amphi does not replace video-call tools such as Teams or Zoom. Video is attached to a talk as a provider link or a stream; see Video recordings and live streaming in Amphi.

The public page is available as soon as the event is created

You create content in the admin, pages publish it, and the site menu makes it reachable for visitors.

The building blocks of an event

Amphi works with four basic kinds of content:

• Talk: title, abstract, time, video, chat.
• Speaker: the speaker can fill the profile in themselves.
• Location: more locations let talks run in parallel.
• Partners: partner and sponsor profiles.

• The page type decides which kind of content you can put on it.
• The layout decides how the content is rendered: grid, list, a selection by tags, or the detail of a single item.
• A conference can have several locations; that is what lets talks run in parallel.
• Speakers and partners are created as profiles first and only then assigned to a page.

Tip: The by tags layout shows only the content marked with a given tag. You can, for example, split speakers into categories and show them separately on their own pages. See Tagging.

Content visibility

Content visibility is handled in several ways:

• by adding a page to the site menu, or removing it,
• by adding content to a page, or removing it,
• with the public / non-public switch on an individual talk or speaker.

Special case – talk accessibility

On top of the basic public / non-public setting, talks let you decide in more detail which visitor gets to see the content of the talk. There are three options:

• Public: anyone can view the content. If you put a live stream of your video into the talk, in theory anyone who lands on the page will be able to watch it.
• Visitors only: the visitor first has to register for the event and can view the content of the talk only after signing in on the public site. More in Attendee and speaker registration.
• Only those registered for the talk: use this option when, for example, the lecture hall has a limited number of seats and you need to make sure no more attendees turn up than there are seats.

Careful: Do not confuse registering for the event and the subsequent sign-in on the public site with signing up for a talk in the sense of “expressing interest in attending a particular talk”.

Amphi offers several predefined layouts for your event's site. Both the public page and the email communication can carry your own branding; see Branding.

If you would like a bespoke design for the public page, we are happy to agree the terms of an Enterprise license with you; see Individual items (Enterprise).

Contact us

• Sending invitations by email
• Creating an invite link

Sending invitations by email

You can import a list of prospective attendees you want to reach into Amphi. Those imported attendees can then be sent an invitation to your conference.

If you have set Amphi up to require registration, you can track how many attendees have already registered and who has not.

You can find out what options Amphi offers for building email templates here.

Amphi does not check on your behalf whether sending the invitation to your recipients complies with your GDPR obligations. More in GDPR and marketing consents.

Invite link

In Amphi you can create an “invite link”. You can place that link on your own website, or use it in any promotional campaigns you run for the conference. Clicking the link takes the user to your conference’s registration page.

Amphi also generates a QR code for the invite link.

Because you can generate several invite links, you can track which one brought you the most registrations.

More about registering users here.

Depending on the content visibility settings of your conference's public page, attendees may be required to sign in. Once signed in, speakers can edit their profile and upload materials for their talks.

Registration is required before signing in.

The registration screen is the same for attendees and speakers.

For everything to work, prepare the following in advance, or at least be ready for it:

• an invitation email template and a default reply-to address
• decide whether you want registration open to visitors
• registration links
• registration screen settings

Invitation email template and reply-to address

The registration process sends out an activation email, so you have to set up its template first.

You set it up in the admin under the Attendee communication and Email templates menu items.

You also need to set a default address that is used when someone replies to an email sent from Amphi.

See Email templates for more.

Open registration

If you set open registration to YES, anyone who lands on your conference's public page finds a registration button and can sign up.

That need not be a problem in itself, but these are so-called organic registrations: you cannot tell where the person came from.

If attribution of registered attendees matters to you, we recommend leaving this set to NO and using registration links instead.

Registration links and invitations keep working even when open registration is set to NO.

The number of registered attendees is capped by your plan. The quota starts at the default value for your plan and you can adjust it up or down. Going over the default number of attendees set by the plan starts automatic monthly recurring billing, see Recurring billing for services. The quota itself is not raised automatically, see Raising quotas.

Registration links

This is an ordinary web link. Clicking it opens the registration screen.

Amphi can track which registration link an attendee came from.

See How to promote your conference for more.

Registration screen settings

There is only one registration screen for all invite links, and it is shared by speakers and attendees alike.

Amphi lets you configure the following properties of the registration screen:

• Required and optional consents. You can edit the wording and link to your own documents, such as your terms and conditions or privacy policy. It is useful for collecting consent to marketing communication, for example. Amphi records what each attendee ticked and what they did not. You can have any number of consents.
• Your own text. You can insert any text of your own. This is how you can achieve implied consent, for example: “By continuing you agree to …”
• Your documents. You can upload a file with your terms and conditions or privacy policy directly, and Amphi displays it right on the page.

Also read how Amphi helps you with GDPR.

Amphi is not a legal advisor. Amphi does not check whether you have properly obtained the consents needed to send a particular type of email.

GDPR from the organizer's point of view

Creating an event forms a contract, and the Data Processing Agreement (DPA) is an integral annex to it. You as the organizer are the data controller and Amphi is the processor.

For details, see the Terms and Conditions and their DPA annex.

What data Amphi processes and for what purposes, how long we keep it and what we do with it, including the list of external partners, is described in our Privacy Policy.

GDPR from the attendee's point of view

It is the event organizer who is responsible for this relationship, as they are in the position of the data controller. It is therefore up to the organizer to assess what purposes they collect personal data from attendees and speakers for, and to inform them accordingly.

To do that, the organizer can publish their privacy policy on one of the pages of the conference's public site, or link to it from the registration process.

The organizer is responsible for making sure that the privacy policy they publish is aligned with the one agreed in the DPA when entering into the contract with Amphi. Individual changes to the privacy policy between Amphi and the organizer are possible on the Enterprise plan only.

You can insert predefined variables into the text to make the email copy dynamic; every recipient then gets an email carrying their own details.

Your logo goes into the email as well; you upload it in Branding.

You can ask your AI for a prompt-generated modern email layout together with the copy. Paste the result into the template field and you have a good-looking email.

Each template also carries the email type, which decides whether it counts toward your limit; see Which emails count toward the limit.

Step by step: building a template with AI

1. 1Copy the sample HTML structure out of Amphi: turn on the Detailed template switch and copy the contents of the Custom HTML layout field.

2. 2Paste the structure into your AI and prompt it for a modern email layout. Ask it to keep the element with id="templateBody" and leave its contents alone.
3. 3Copy the generated HTML back into the Custom HTML layout field.
4. 4Save the template and use the email preview to check that the body shows up in the right place.

The generated HTML must keep the element with id="templateBody"; that is where Amphi injects the email body.

Tags play two different roles in Amphi. Do not mix them up; they are set up in different places and serve different purposes.

• Attendee tags: the audience assigns them during a session, and you then talk to one segment only.
• Content tags: you mark speakers or sessions with them and the public page shows only what carries a given tag.

Attendee tags

1. 1Before the event, the organiser or the speaker prepares a set of tags. Sports, for example: football, ice hockey, squash.
2. 2During the session attendees can tag themselves with the prepared tags through a chat interaction, which the speaker can prompt them to do.
3. 3After the event you have a segmented audience. You can export the tagged attendees, or send them an email.

Tags are collected through the chat. With chat switched off for a session, an attendee has nowhere to pick a tag.

Targeted communication by tag

Pick a tag people assigned themselves, write a template, and Amphi sends the email to that segment only. Feedback collection can be aimed the same way: at everyone, or at one tagged segment.

Emails aimed at a tag are of the Custom category, so they count toward the limit set by your plan; see Which emails count toward the limit.

Content tags on the public page

You can tag content as well: speakers or sessions. The by tags layout then shows only the items carrying that tag, so you can split speakers into categories and give each its own page. See Publishing conference content.

Tags do not work in archive mode; emails by tag cannot be sent.

Tags are available on every plan, Free included.

• Your logo, shown on the event’s public site and available for use in email templates
• Primary and secondary color settings
• A custom domain in the URL (paid plans only)

If you want more extensive brand changes, or a public site tailored to your needs, take a look here.

Amphi is built around several ways to attach video to a talk. The first one works today; the other three are on the way.

Embedded links

The video stays with the provider you already use; you only paste its link into Amphi. The player then shows up right in the talk detail, but the file itself never sits with us: storage and bandwidth stay on the provider's side. In practice it means copying the video's address and pasting it into the talk.

Supported providers:

• YouTube, including YouTube Live
• Vimeo
• Microsoft Teams
• Zoom
• Google Meet
• Free-form iframe: any web page, so any other provider that offers an embed code for the video works too

Coming soon

• Video file upload: upload the video straight into Amphi and we take care of hosting and playback.
• Live playback from your own source (RTMP): push the stream from your broadcasting software to an RTMP address and Amphi shows it in the talk. This is how you bring a running video call into Amphi, for example on Teams or Zoom. Your production crew can push camera feeds to the RTMP endpoint the same way. You cannot interact with the running call from Amphi. You are there as an observer.
• Automatic recording of the broadcast: the incoming RTMP stream is recorded as it runs, so the talk keeps the recording afterwards with no extra work.

Video-hour limits apply to every option except embedded links; a pasted link does not consume video hours at all. For details see Raising quotas.

To access the API, first generate an access token in the Amphi settings. The token works as your “login credentials”: anyone who has it can work with your account through the API, so don't share it with anyone.

All available operations are described in our Open API documentation.

• “Create a talk on July 17 from 8:00 titled XY and generate the abstract in the description from the attached presentation.”
• “Invite these 50 attendees using the emails in the attachment and use the sample invite email as a template.”
• “Update speaker Jane Doe's bio from her LinkedIn profile and add a link to the uploaded presentation.”

How to set it up

Amphi can be connected to a range of AI tools. Each one is set up a little differently, so we don't walk through it step by step here; we assume you know your tool. The main difference is whether your AI assistant supports MCP or not.

Your tool supports MCP

Copy the MCP URL from the Amphi admin and add it to your tool as a new connector. The assistant can then work with your events. How to add a connector is covered in each tool's documentation:

• Claude
• Claude Code
• Cursor

Your tool doesn't support MCP

Some tools (or some of their plans) don't support MCP. In that case, you go through the regular API instead. Generate an access token in the Amphi settings and give it to your tool. The tool then reads the Amphi Open API documentation and calls the API on your behalf.

The AI assistant works with the same permissions as the account it is connected to. Don't share the token with anyone, and review the changes the AI makes before you publish them.