E-sign beta is in Private Preview, available only to the existing beta tester group. The signing steps below apply only to those organizations. Signing up, paying, upgrading, contacting support, viewing a public demo, or accepting a portal invitation does not grant E-sign access.
Signing contracts
Contracts shared with the customer’s authorized portal contact appear on the Contracts page and the event’s Contracts tab. The current web sending workflow supports one client signer: the linked customer’s primary contact.1
Open the contract
The client selects Review & sign on a contract that’s ready for signature.
2
Open the signing experience
For a hosted request, select Open signing page to open SignWell in a new tab. When an embedded request is available, the SignWell signing window appears inside the portal. SignWell records the signature against the document with an audit trail.
3
Done
After signing a hosted request, return to the portal so it can refresh the status. Once the signature is recorded, the contract shows a signed state with the date. An already-signed contract confirms it is complete.
Existing E-sign testers with the required entitlement and configuration can use white-label branding. The portal has no separate decline action; questions about terms should go to the booking team. See contracts & e-signatures for status and resend behavior.
Reviewing invoices
The Invoices page gives the client a plain view of the deposits, balances, and payment requests your booking team has shared. Each row shows an amount, a due or paid date, and a status. The dashboard also summarizes their open balance and recent invoices at a glance.The portal shows invoices for the client to review. It isn’t a checkout. Collect client payment through your usual payment collection process; the portal keeps the client informed of what’s due and what’s settled. Gig payouts are the separate workflow for paying crew.
Filling out forms
Forms you assign to a client (questionnaires, intake, or feedback) appear on the Forms page and on the relevant event, each showing its purpose, any due date, and whether it’s still required or already submitted.1
Open the form
The client selects Fill out on a form that still needs a response.
2
Complete it in the portal
The form opens embedded in the portal under your branding. Answers go straight to your booking team on submit.
3
Submission is confirmed
The portal confirms the response. For JotForm forms this happens the instant the client submits; for Form.io forms it confirms once the response reaches Soundcheck. Either way it’s recorded against the right customer or event.
Portal forms
How your team builds forms in JotForm or Form.io and assigns them to clients.
Following updates
Each event has a Messages area for viewing available updates. The portal’s Messages page routes the client into the event they want to review. The current portal does not provide a message composer; reply through the contact method agreed with your booking team. Crew Chat is a separate Private Preview. Every event workspace also shows the notes and any files your team has shared for that event, so the details a client needs travel with the event rather than living in someone’s inbox.A note on what’s shared
Clients only ever see what’s tied to their own customer record: their events, their contracts, their forms, their invoices. You control what appears by linking gigs to the customer and assigning forms and contracts. When in doubt about what a specific client will see, preview their portal first.Related pages
Client portal
The full picture of what clients see.
Contracts & e-signatures
How contracts move from sent to signed.
Inviting clients
Get a client into the portal.