Legal Tech and AI

Shared Inboxes and Ticketing for Client Requests

Set up a shared inbox and ticketing for client requests: what to route in, ticket fields, status rules, response targets, macros and a weekly review.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. The problem a shared inbox solves
  2. The duty behind the process
  3. What to route into the shared inbox
  4. Ticket fields
  5. Response targets by request type
  6. Set it up in six steps
  7. Macros that save time
  8. After-hours and urgent requests
  9. Example: one week in the queue
  10. Mistakes to avoid
  11. The weekly review
  12. Privacy and access
  13. Frequently asked questions
  14. References
Legal Tech and AI: Shared Inboxes and Ticketing for Client RequestsArticle coverLEGAL TECH AND AIShared Inboxes andTicketing for ClientRequestsAva for LawyersInsightsLegal Tech and AI: Shared Inboxes and Ticketing for Client RequestsArticle coverLEGAL TECH AND AIShared Inboxes andTicketing for ClientRequestsAva for Lawyers

Key takeaways

  • Model Rule 1.4 requires lawyers to keep clients reasonably informed and to promptly comply with reasonable requests for information[1].
  • In a 2024 secret-shopper study of US law firms, only 33% replied to emails[2].
  • Every request needs one owner, a status and a due time that the whole team can see.
  • Review overdue and reopened tickets weekly; they show exactly where the process breaks.

The problem a shared inbox solves

Client requests arrive by email, phone messages, portal notes, texts and web forms, and most of them land in someone's personal inbox. When that person is in court, on vacation or gone, the request waits, and the client only finds out when they chase. Prospects are treated the same way: in Clio's 2024 secret-shopper study of 500 US law firms, only 33% of firms responded to emails, down from 40% in 2019[2].

Unanswered requests cost trust, and trust in the profession is already thin. In Gallup's December 2025 poll, only 20% of Americans rated lawyers' honesty and ethical standards as high or very high, while 34% rated them low or very low[3]. Prompt, visible responses are one of the few things a firm controls that move that perception, one client at a time.

How Americans rate the honesty and ethics of lawyers, 2025
How Americans rate the honesty and ethics of lawyers, 2025Stacked bar chart. High or very high: 20%; Average: 46%; Low or very low: 34%.High or very high: 20% (20%)Average: 46% (46%)Low or very low: 34% (34%)How Americans rate the honesty and ethics of lawyers, 2025Stacked bar chart. High or very high: 20%; Average: 46%; Low or very low: 34%.High or very high: 20% (20%)Average: 46% (46%)Low or very low: 34% (34%)
  • High or very high 20%
  • Average 46%
  • Low or very low 34%

Source: Gallup, 2025[3]

Show the data
ItemValue
High or very high20%
Average46%
Low or very low34%

The duty behind the process

ABA Model Rule 1.4 requires lawyers to keep clients reasonably informed about the status of their matter and to promptly comply with reasonable requests for information[1]. A shared inbox does not change who owes that duty. It makes it possible to show that every request was seen, assigned and answered, and it stops the duty depending on one person's memory.

It also changes the conversation inside the firm. Instead of asking "did anyone reply to Mrs. Chen?", the managing partner can see the answer, who owns it and when it is due.

What to route into the shared inbox

  • A general client-services email address printed on letters, invoices and the website.
  • Phone messages taken by reception or an answering service, entered as tickets rather than sticky notes.
  • Client portal messages and web form submissions.
  • Texts sent to the firm's business number.
  • Requests that staff receive personally but that someone else must handle, forwarded into the queue instead of left in a personal inbox.

Keep internal strategy out of it. The shared inbox is for client requests and responses, not for lawyers discussing case strategy, which belongs in the matter file with tighter access.

Ticket fields

Keep the fields short. Every extra field is one more thing people skip when they are busy.

Minimum ticket fields for client requests
FieldPurposeExample value
Client and matterLinks the request to the fileExample: Chen v. Rivera
Request typeDrives routing and the response targetStatus update, document request, billing question, scheduling
ChannelShows where requests come fromEmail, phone message, portal, text
OwnerOne named person accountableThe paralegal assigned to the matter
DueWhen a substantive reply is promisedEnd of the next business day
StatusWhere the request standsNew, assigned, waiting on client, waiting on attorney, done
Resolution noteWhat was done, for the fileSent the confirmed hearing date and a checklist

Response targets by request type

Set targets you can meet every week, then tighten them once the team is consistently hitting them. A target missed every Monday is worse than a slower one that is always met, because clients plan around what you tell them. Example targets for a fictional eight-person firm:

Example response targets
Request typeAcknowledgeSubstantive reply
Urgent: court date, deadline, arrest or safetyWithin one business hourSame day, with an attorney involved
Status updateSame business dayWithin two business days
Document request or upload problemSame business dayWithin one business day
Billing questionSame business dayWithin three business days
SchedulingWithin two business hoursSame day

Separate acknowledgment from answer. An acknowledgment that names the owner and the due time is itself useful to a client, as long as the substantive reply then arrives when promised.

Set it up in six steps

  1. Choose the tool

    A shared mailbox with assignment and statuses can be enough for a small firm; ticketing software adds due dates, routing rules and reports.

  2. Define request types and owners

    Start with six or fewer types and assign default owners by practice group.

  3. Write acknowledgment templates

    Each says the request was received, who owns it and when to expect a reply.

  4. Route every channel in

    Forward the general email, connect the portal and have reception log phone messages as tickets.

  5. Train for one rule

    Nothing gets answered from a personal inbox without being logged in the queue.

  6. Go live with daily huddles

    For the first two weeks, spend ten minutes each morning on unassigned and overdue tickets.

Macros that save time

Templates speed up the routine replies, but they only work if staff edit them to answer the actual question. Example macros:

  • Example status update: "Thanks for checking in. The current step is the exchange of documents with the other side. The next date is the hearing on the date in your portal. Your paralegal will update you by Friday."
  • Example waiting-on-client message: "To move forward we need your last two pay stubs. You can upload them in the client portal. We will follow up on Wednesday if we have not received them."
  • Example billing reply: "Thanks for your question about your latest invoice. Our billing team will reply by Thursday with a breakdown."

Review macros quarterly. A template that mentions an old portal, a staff member who left or a process that changed does more harm than writing from scratch.

After-hours and urgent requests

A shared inbox does not make anyone available at midnight, and clients should not think it does. Say in the auto-acknowledgment when the queue is monitored, give an emergency route for genuinely urgent matters, and make sure that route reaches a person. Tickets that arrive overnight are triaged first thing: urgent ones flagged to an attorney, the rest assigned before the morning huddle.

Watch for urgent requests sent through slow channels. A client who emails at 6 p.m. to say they have been served with a hearing notice for the next morning needs a call, not a ticket due in two days. Train whoever triages to read the content, not just the request type.

Example: one week in the queue

Example: a fictional eight-person firm moves its client-services email and phone messages into a shared ticketing tool. In the first week the queue receives 140 requests. Most are status updates and document problems; a handful are billing questions. Three tickets go overdue, all owned by one paralegal who was in a two-day trial. The weekly review moves default ownership for that practice group to a pair of paralegals so one person's absence no longer stalls a whole caseload. It also finds that many document problems come from one confusing upload page, which the firm rewrites. Document tickets fall sharply the following week.

Mistakes to avoid

  1. Creating too many request types, so staff pick the wrong one or none.
  2. Assigning tickets to a group rather than a person, so everyone assumes someone else has it.
  3. Closing tickets when the acknowledgment goes out rather than when the question is answered.
  4. Letting lawyers opt out of the queue, which recreates the personal-inbox problem.
  5. Never reading reopened tickets, which are the clearest signal that replies are missing the point.

The weekly review

  1. Tickets overdue against target, by owner and request type.
  2. Tickets reopened because the client wrote again, which reveal replies that did not answer the question.
  3. Request types that grew this week, which often point to a process gap such as confusing invoices or a broken upload link.
  4. Requests that arrived outside the queue and were found later.
  5. One fix to make before next week, with an owner.

Small firms already work long hours; some lawyers work more than 40 hours a week[4]. A visible queue spreads the load across the team rather than relying on whoever happens to remember, and the weekly review keeps the same problems from recurring.

Privacy and access

A shared inbox concentrates client information, so lock it down. Give access only to staff who work on client matters, require multi-factor authentication, and use role-based views if one practice group should not see another's clients. Apply your retention schedule to tickets as well as emails, and make sure a departing employee loses access the day they leave.

For the channels that feed the queue, see texting platforms for law firms and video conferencing security. If you want to trial a ticketing tool before committing, follow our technology pilot method, and fund it through your technology budget.

Frequently asked questions

Do small firms need ticketing software?

Not always. A shared mailbox with assignment, statuses and a daily check can work for a few people. Ticketing tools help once volume or team size makes it hard to see what is overdue.

Should clients still email lawyers directly?

They will, and that is fine, but requests should be logged in the shared queue so someone else can respond when the lawyer is unavailable.

What response time should we promise?

Promise what you can meet every week, such as same-day acknowledgment and a substantive status reply within two business days, and handle urgent matters separately.

Is a shared inbox confidential enough?

It can be. Restrict access to staff who work on client matters, require multi-factor authentication and keep internal strategy discussions out of it.

References

  1. American Bar Association (2026). Rule 1.4: Communications, ABA Model Rules of Professional Conduct (archived copy) (opens in a new tab) โ†‘

  2. Illinois Supreme Court Commission on Professionalism (2Civility) (2024). Phone Calls Ignored, Emails Unanswered: Fixing the First Impression Problem for Law Firms (opens in a new tab) โ†‘

  3. Gallup (2025). Nurses Continue to Lead in Honesty and Ethics Ratings (opens in a new tab) โ†‘

  4. U.S. Bureau of Labor Statistics (2025). Lawyers: Occupational Outlook Handbook (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo