Stop losing work to scattered inboxes

Q: 01 - Replace scattered requests with a single structured form

A shared form gives everyone (clients and internal teams) one reliable way to submit work, with all the details you need already included.Create a Form for your most common request types (design briefs, content updates, feature requests).Map each field to a task property — title, description, assignee, due date — so submissions become tasks automatically.Route each form to the correct project or task list so requests land exactly where they belong.Use conditional fields to show only relevant questions based on the type of request.

Every project starts with a request. A centralized intake process means every request is captured, structured, and ready to act on, before it falls through the cracks.

Delivering projects

Read time

8 minutes

Goal

Streamline intake

Primary Tool

Forms & Teamwork Desk

Why this matters

When requests arrive through emails, chat messages, and verbal handoffs, work gets missed, context gets lost, and projects start late. Structured intake fixes that.

Outcome

One place for every request

Every request is logged, visible, and trackable, no matter how it arrives or who it came from.

Helps you

Reduce back-and-forth rework

Structured intake captures the right details upfront, so your team spends less time chasing information.

Unlocks

Forms & Teamwork Desk

Without centralized intake, requests arrive incomplete, get lost, or never make it into your project system at all.

Key actions

01 - Replace scattered requests with a single structured form

A shared form gives everyone (clients and internal teams) one reliable way to submit work, with all the details you need already included.

Create a Form for your most common request types (design briefs, content updates, feature requests).
Map each field to a task property — title, description, assignee, due date — so submissions become tasks automatically.
Route each form to the correct project or task list so requests land exactly where they belong.
Use conditional fields to show only relevant questions based on the type of request.

02 - Turn every client email into a trackable work item in Teamwork Desk

When requests live in personal inboxes, they're invisible to the rest of your team and easy to miss. A shared inbox makes every message visible and assignable.

Set up a shared inbox (e.g. requests@, support@) so all incoming messages are centralized.
Convert emails to tickets that can be assigned, prioritized, and tracked.
Use canned responses to standardize replies and internal notes to keep context in one place.
Set up SLAs so your team always knows which tickets need attention first.

03 - Move complex tickets into project work without manual handoffs

Not everything that arrives as a quick ticket stays one. As work becomes more complex, it should be structured as a project rather than relying on manual handoffs.

Escalate tickets to tasks or projects when work requires more than a quick fix.
Connect Desk and Projects so the full client communication thread stays linked to the work it generated.
Use task templates to standardize the structure for common escalation types.

04 - Automate the handoff from request to actionable task

Manual triage is where requests get dropped. Automation removes that step. Every submission arrives structured, assigned, and ready to work.

Set up automation to create a task automatically from every form submission.
Configure defaults (assignee, priority, due date) so every incoming task arrives ready to go.
Save form templates for recurring request types to keep intake consistent as your team grows.

Key concepts

Forms vs. Desk
Forms are for structured, proactive requests where clients or teammates fill in details you define upfront. Desk is for reactive communication covering messages that arrive through email channels you don't control. Use both for full coverage.
Requests vs. tickets vs. tasks
A request is something someone needs. A ticket is that request captured and tracked. A task is the unit of work your team executes. The goal of intake is to make the journey from request to task fast, structured, and automatic.

Best practices

Do this
- Map form fields to task properties so every submission is immediately actionable.
- Set up a shared inbox before going live — personal inboxes break team visibility.
- Save form templates for your most common request types to keep intake consistent.
- Automate form-to-task creation to remove the manual triage step entirely.
Watch out for
- Using personal email for client requests. Messages get lost and there's no team visibility.
- Creating forms without routing them. Unrouted submissions have nowhere to land.
- Skipping automation and relying on manual triage. That's where requests get dropped.
- Leaving task defaults unconfigured. Submitted tasks arrive with missing assignees or dates.

Stop losing work to scattered inboxes

Why this matters

Outcome

Helps you

Unlocks

Key actions

Key concepts

Forms vs. Desk

Requests vs. tickets vs. tasks

Best practices

Do this

Watch out for

Next steps

Work intake

Teamwork Desk foundations

The robust and refreshed Resource Scheduler