Messages Between Pages

An artist, a venue, a promoter or a crew writes to another page in its own name. The conversation belongs to the two pages, not to the people: everyone who answers for a page reads it and can reply, and somebody who leaves the team leaves the conversation with it.

Who answers for a page

The permission is Answer pro messages, alone in the Pro messaging group of a page's Permissions screen. Whoever holds it reads the page's conversations with other pages and answers them in its name. The page's owner holds it, and so do the people given Admin Template or Manager Template.

For a crew, the same feature sits in the crew's roles: the shipped Owner, Admin and Manager roles carry it. It lets a member write in the crew's name, and answer for the roster pages they are assigned to.

Without it on any page, New then A page says No page to write as.

Start a conversation

1. Click New at the bottom of the inbox, then A page.
2. Under Write as, pick the page you write for.
3. Under To, type at least two letters of an artist, a venue or a promoter, and pick it.
4. Read the trust panel, then write Your message.
5. Click Send.

Three other places open the same form with the page already picked:

• Contact, on the card Write to and the page's name, on an artist, venue or promoter page of sway.events, when you are signed in and answer for another page;
• Write, on a row of an event's line-up: the conversation is about that event;
• Write about it, in a booking's panel on Bookings: the conversation is about that booking.

From a line-up or a booking, Write as already shows your page that takes part in it.

A conversation about an event or a booking shows it under its header, such as About the event: and the event's name and date. Each event or booking gets its own conversation between the same two pages; without one, the two pages share a single conversation.

A first message is a request

Two pages that never worked together on Sway start with a request: the first message goes through, and nothing more until the other page accepts it. Sending says Request sent. You can write again once it is accepted.

The pages count as having worked together, and write freely, when:

• they already accepted a conversation with each other;
• one is a crew and the other is on its roster, shared with it, or a promoter it confirmed a booking with;
• both are on the same crew's roster;
• an artist and a promoter have a confirmed booking together;
• two promoters co-organise an event, the invitation accepted.

On the other side, the request arrives under Requests, with a Contact request in the bell. The conversation opens on what the page needs to decide: the sender's message, the trust panel, and three answers.

• Accept: the conversation opens, the thread says the page accepted it, and the sender is told: Request accepted.
• Ignore: the request moves under Archived. The sender is not told, and you can still accept it from there.
• Block: see Block a page.

Limits on requests

A page sends up to 20 requests a day and 100 every 30 days, and one person up to 40 a day across all their pages. When more than 70% of a page's last 20 requests were ignored, blocked or left unanswered for 30 days, its limits halve. Past the limit, sending says Too many new conversations today. Try again tomorrow.

Pages that already worked together are not counted: only requests are.

What the trust panel shows

Beside a request, and in the form once you pick a page, the trust panel says what Sway knows about it:

• Sway Verified page, or Page not verified;
• On Sway since a month and a year;
• how many published events it has on Sway, its roster's for a crew;
• how fast it usually answers, from Usually answers within an hour to Usually answers within a few days, once it has answered five conversations other pages started in the last 90 days.

It ends on a line worth reading twice: Never pay a deposit before you know who you are talking to.

A page nobody manages yet

Pages created by an event's credits often have nobody behind them yet: the search marks them Not on Sway yet. Picking one says Nobody answers for this page on Sway yet and offers Copy the invitation link instead of a message field. The link opens the page's claim form: send it through the channel you already use with them. Once they claim the page, your messages reach them.

Nothing is sent and nothing is kept until then.

Work as a team

• as and a page name, under the header, says which page you answer as.
• Note, beside the message field, turns the next message into an Internal note: only your side's team reads it, and the other page never sees it.
• Assign to a teammate, in the conversation's menu, hands it to someone who answers for the page. They are told: Conversation assigned. The header then reads assigned to and their name.
• The status, in the same menu: Mark as waiting for a reply, Mark as done, Archive, and Reopen. Each page files the conversation on its own side. Done or archived, it moves under Archived; a new message from the other page brings it back.

Block a page

Block on a request, or Block this page in the conversation's menu, asks Block this page? first. A blocked page can no longer write to yours, nor start a new conversation with it, and it is not told: on its side, the conversation simply waits. The conversation moves under Archived.

Unblock, in the menu or under the thread, lifts it.

Where the rest lives

• Offers: booking terms in the conversation.
• Write in a conversation: notes, files, mentions and Swapy.
• Team and Permissions: who holds Answer pro messages on a page.
• Privacy and safety: scam alerts and reports.