Felagar is also available in your language.
Features
Define intake forms, collect structured requests from the portal, and close the loop with email when needed.
In practice
Define request types with the fields your studio needs. Clients submit from the portal; tickets open with a structured payload and a readable first message. Email keeps the loop open when someone is away from the board.
Intake turns vague asks into structured work. You own the form fields, clients submit cleanly from the portal, and email keeps the loop alive when someone is away from the board.
What stands out when this becomes part of how you run client work.
Agency-defined intake forms and required fields
Inbox for the studio, portal for clients
Email in and out when you need it
Tickets turn ad-hoc asks into trackable work. You own the form fields; clients submit cleanly; email keeps replies moving.
Build intake forms under Settings → Intake or per company, with the fields and required inputs your studio needs.
Clients submit from the portal. Each ticket opens with a structured payload and a readable first message for the studio inbox.
Assign, reply, and move the ticket through your studio workflow until it is done.
Use email in and out when someone is away from the board, so the thread does not stall in a tab they never open.
Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.