Track the work your customers create.
A board holds leads, tickets, or jobs with fields and statuses. Your team moves them, and Procedures update them where you allow it.

Keep the customer and the work together.
Link an item to a contact and the conversation comes with it, next to the fields, comments, files, and every change.

The item and the customer, on one screen.
Status, assignee, and your fields on top. The customer's messages underneath.

See what changed, and who changed it.
People, Procedures, and customer replies all land in the same log.
Fields and statuses
Set up the fields your work needs.
Linked customer
Messages from any channel show on the item.
Comments and files
Notes and photos stay with the job.
Activity log
Every change, with who made it.
Assign it, then move it to Done.
Every item has an owner and a status. Look at the same board the way that suits the work.
Assign a teammate
Assignees are people, so someone always owns the job.
Move it forward
Change the status on the board or from the item.
Same items, three views
Kanban by status, a grouped list, or a table of fields.
Review board email before it becomes work.
Nothing turns into an item on its own. A person on your team decides what belongs on the board.

An email comes in
A customer emails about something that isn't on the board yet.
It waits in Intake
Email that doesn't match an item stays there for a person to review.
Someone accepts it
Accept it as a new item, or link it to one that already exists.
Let agents write only where you allow it.
Agent writes stay off on a board until you turn them on. Then Procedures can create items, update fields, add notes, and move statuses.

One switch per board
Turn on agent writes for the boards that need them. The rest stay with your team.
Create items
A Procedure can open the item when a call or chat turns into work.
Update the item
Fields, notes, and status, each change in the activity log.
Keep some fields for people
Mark a field Humans only, and agents and Procedures can't change it.
Start a Procedure when an item changes or stalls.
A Procedure is a set of steps your agents follow. On a board, it can start from what happens to an item, or from how long it's been waiting.
When something happens on an item
Pick the event: an item is created, a status or field changes, someone is assigned, or a message, file, or comment is added.
When an item sits too long
Set a time in a status, like three days in Scheduled, and the Procedure starts when an item crosses it.
Then it does the next step
Message the customer, wait for a reply, update the item, or hand it to a teammate with a note.
Wait for the right person to approve.
A Procedure can stop and ask the people you name. It picks up again once they approve or reject.

On the item.

Through a link.
Mention @Ally on an item.
Ask what the customer said, or hand off a task. Ally reads the item and its messages, and acts with your permissions.

Ask on the item
Mention @Ally in a comment with a question or a task. Ally replies in the comments.

Keep going in chat
Continue in Ally picks up the same thread, with the item and the customer already there.
Questions, answered.
Still unsure? Talk to a human.
Still unsure? Talk to a human.

Put your first board to work.
Set the statuses and fields, then assign the first job. 14 days, no credit card.

