DocketPilot

Sign in with your own staff account.

Forgot your password? Ask an admin to reset it.

DocketPilot — Staff Console

Minimal admin panel over the scheduling API. Every action here is a thin wrapper around a real backend call — nothing is simulated. Results appear in the log at the bottom of the page.

Signed in as
Your account is view-only: you can look at cases, requests and the log, but you can't create or send anything. Ask an admin if you need scheduler access.

Staff accounts (admin)

Add a staff member

Each person signs in with their own email and password. Every approval, request and change they make is recorded under their name.
Scheduler: create, approve and send requests. Viewer: read-only. Admin: everything, including managing staff and firm setup.

Current staff logins
Loading…

1. Create your firm (one-time setup)

Organization

Copy the returned id below — you'll need it for MYCASE_ORGANIZATION_ID in your .env if using MyCase, and for every case/mailbox you create next.

Scheduling mailbox & persona (Growing Firm / Enterprise: create more than one)

Most firms need exactly one. Growing Firm and Enterprise accounts can create additional ones \u2014 e.g. one per office or practice group \u2014 and assign specific cases to whichever identity fits. The very first mailbox you create for a firm automatically becomes its default.

Assign the persona for a mailbox
Point a specific case at a non-default persona

Only needed if this case should send under a different identity than the firm's default \u2014 e.g. a case belonging to a specific office. Leave a case unassigned and it always uses the firm default.

2. External firms (grouping outside contacts by who they work for)

Create an external firm

Lets a reply from ANY person linked to this firm count as that firm responding \u2014 no designated primary contact, everyone listed is equally valid. Create the firm first, then link people to it below when you add them.

View a firm's roster

3. Add a person

Person

4. Case details

Case

This happens once per matter \u2014 it's the permanent record everything else (participants, cleared dates, every scheduling request you'll ever make for this case) hangs off of. When setting up a new scheduling request later, you'll select this case rather than create it again.

Or: a lead (no open case yet)

For scheduling with a prospective client or the other side before anything is formally filed. Supports meet-and-confers, client meetings, and mediations only \u2014 hearings and depositions need an actual open case, since those require a court and a filed matter. No case number needed; one's generated automatically.

5. Recipients & CC

Recipients \u2014 external parties who actually get emailed and need to respond
CC \u2014 your own firm's team, copied automatically on every scheduling email for this case

6. Clear dates (hearings & depositions)

Cleared availability windows

Dates don't need to be consecutive — add as many separate date/time windows as have actually been offered or set aside, then clear them all in one action.

7. Create & trigger a scheduling request

New scheduling request

Recipient (opposing counsel). Pick someone already known on this case, or add a new one by email — selecting a case above fills in who's already on file so you're not retyping the same contacts every time.

Give recipients context. Especially useful for meet-and-confers \u2014 explain what this is actually about, and/or attach a letter or PDF, so the recipient isn't scheduling into the dark. Sent on the first email only.

Or: multiple depositions in one request (list each witness + time block)

For deposing several witnesses in one sitting \u2014 give each their own name and an explicit start/end block so nobody's deposition gets scheduled over another's. Add this to a deposition-type request created above (enter its ID below).

Fire the trigger / check status


  

Not at your desk? Instead of the checkbox above, have this reviewed by email \u2014 reply APPROVED or DECLINE from your own inbox, no login needed.

8. Forwarded scheduling inquiries (outside office reached out first)

Submit a forwarded inquiry

When an outside office emails asking to schedule something, forward that email to the scheduling mailbox (or paste it below for now, until real mailbox monitoring is wired up). The system tries to match it to an existing case automatically \u2014 if it can't, it'll show up below for you to link manually.

Inquiries needing staff review
Clarify which case an inquiry is about

For any inquiry the matcher couldn't confidently resolve on its own. Just say which case, event type, and attorney this is about \u2014 no need to set up a date range, that's computed automatically. The scheduler replies directly in the same email thread the outside office started; it still goes through the normal review + trigger steps above before anything actually sends.

Or have someone else confirm this plan by email instead of doing it here directly \u2014 fill in the case/event type/attorney/duration above first, then send it to them for a reply-only approval.

9. Practice management integration (MyCase)

Connect MyCase

One-time, firm-wide \u2014 an admin with the "manage preferences, billing, and payment options" permission authorizes once, and it covers every attorney's calendar for the whole firm. This does NOT need to happen per attorney.

Checking status\u2026

10. CC-monitored conversations (e.g. mediator selection \u2192 dates)

Submit a message for observation

For threads that don't start as a scheduling ask \u2014 a mediation request typically opens with negotiating WHO the mediator will be. CC the scheduling mailbox on the whole thread from the start (or paste each message below for now). It watches silently and only flags once a message looks like the conversation has shifted to dates \u2014 it never sends anything on its own.

Threads flagged as ready for scheduling
Hand off a flagged thread

Confirms this is actually ready \u2014 creates a draft request, threaded to reply right where the conversation left off. Still goes through the normal review + trigger steps above before anything sends.

11. Background jobs (normally run automatically every 5–30 min)

Manual run — useful before you trust the cron

Log