Setup, guides and an email that gets answered

A system with many options is only good if it is set up right. That is why we build the event together with you, and that is why there are written guides and videos for the day to day work on support.crewstack.io.

We set it up together with you

You do not start from an empty screen. We go through your structure and build the event before you invite the crew.

A walkthrough of your structure

Teams and team groups, user types, what you need to know about the crew, and which rules apply to shifts, accreditation and catering. That conversation is what decides how the rest is set up.

Setting up the event

Registration forms, email templates, passes, products and the crew portal are set up to fit your event and your design. Your own domain and your own layout are part of the setup.

Reuse for next year

Schedules can be pulled in from an earlier event and placed on new dates, forms can be cloned, and the teams can invite last year's crew again. The second year is faster than the first.

When you need help along the way

Most of it can be looked up. The rest we answer, and during the event we know perfectly well that a question about a schedule at 10pm cannot wait a week.

Guides and videos

Written guides and video walkthroughs for teams, schedules, accreditation, guest lists, products and the crew portal are on support.crewstack.io and can be shared with your team leads.

Email support

Write to us when something does not behave the way you expect. We aim to answer within one working day. If you are in the middle of an event, put that in the subject line.

A named contact by agreement

By agreement you get a named contact who knows your setup and follows the event from planning to execution. Then you do not have to explain your structure from scratch every time.

The system does not stand still

Much of what gets built comes from organizers who asked for it. The changes are written down, so you can see what has happened since last time.

Changelog every month

New features and fixes are described every month in our changelog, so you can see what has arrived since your last event.

Requests from organizers

A large part of the development comes from concrete requests from the events that use the system. Tell us what is missing in your workflow.

Experience with running events

Crewstack has run large Danish events since 2014. We know the difference between a question in January and a question during the build week.

In short

<1 day
Response time on email, which we aim for
Every month
New features and fixes in the changelog
Since 2014
In operation at Danish events

Shall we set up your event together?

We start with a demo, where we look at your teams, shifts and guests, and agree from there what the setup takes.