Your application inbox

Everyone reaching out to you arrives at /applications/, whether they applied through a listing or project on the platform or sent you an email.

Two ways applications arrive

• In-platform — someone applies through your listing or project and their answers land structured, against the right form.
• By email — inbound email is turned into an application in the same inbox, so you are not working two systems. Inbound email is a plan-controlled capability.

Statuses

• In Discussion — you are engaging with them.
• Accepted — you are going ahead.
• Rejected — not this time.

Move applications between statuses as you work through them, so the inbox reflects reality rather than becoming a backlog you scroll.

Working an application

Open one to see the answers, attachments, and history in a single view. From there you can reply by email, run AI analysis to get a summary and fit score, or move the person onto your roster if the relationship is worth keeping beyond this one approach.

Keeping it manageable

• Set a status on every application you open — decide once rather than twice.
• Ask Spotty to count or search your applications rather than scrolling: "how many in discussion on the festival project".
• Reject kindly and promptly. The person may be right for the next thing.

Settings and export

Inbox behaviour is configured at /applications/settings/, and you can export applications to CSV from the inbox.