ServerHub: Agent Guide

Accessing ServeManager & Working Your Jobs

Who is this guide for? Process servers and agencies using ServerHub to receive, work, and complete service of process jobs inside ServeManager.

1. Overview

As a ServerHub agent (process server or agency), you receive service of process jobs from Agencies who have connected with you through the ServerHub directory. All job work — reviewing details, recording attempts, generating affidavits, and receiving payment — takes place directly inside ServeManager.

Your Workflow at a Glance

Step	What Happens
1. Account Setup	Create your ServeManager account and set up your ServerHub profile
2. Wallet Setup	Verify your Dwolla wallet to receive automatic payments
3. Agency Connection	An Agency finds your profile and sends a connection request
4. Receive Job	Agency assigns a job — you get notified and review the details
5. Attempt Service	Record each service attempt with date, time, location, and outcome
6. Sign the Affidavit	Agency will create the affidavit, simply sign and share
7. Get Paid	Payment transfers automatically from the client’s wallet to yours

Everything happens in ServeManager You do not need any separate app or tool. ServeManager is accessible via web browser at servemanager.com, and via the ServeManager mobile app for recording attempts in the field.

2. Accessing ServeManager

Web Access

ServeManager is a web-based platform accessible from any modern browser. To log in:

1. Go to servemanager.com
2. Click Sign In in the top-right corner
3. Enter your email address and password
4. You will land on your account dashboard

First Time Logging In? You will receive an email invitation from your account administrator or from ServeManager directly. Click the link in the email to set your password and activate your account. The link expires after 48 hours — contact your admin if it has expired.

Mobile App Access

The ServeManager mobile app is the recommended tool for working jobs in the field. It allows you to view job details, record attempts with automatic GPS capture, upload photos, and sign affidavits on your device.

Platform	How to Download
iOS (iPhone / iPad)	Search “ServeManager” in the Apple App Store
Android	Search “ServeManager” in the Google Play Store

• Log in with the same email and password as the web version
• Enable location permissions when prompted — required for GPS capture on attempts
• Enable push notifications to receive alerts when new jobs are assigned to you

3. Receiving a Job

How Jobs Are Sent to You

When a connected client assigns a job to your account, ServeManager automatically notifies you. You will receive:

• An email notification to your registered address
• A push notification on the mobile app (if enabled)
• An in-app alert visible in your Notifications panel

Reviewing Job Details

When you receive a new job, open it from your Jobs dashboard to review all details before accepting:

Field	What to Check
Recipient Name & Address	Confirm the service address is within your coverage area
Documents to Serve	Download and review the attached documents before heading out
Due Date	Note the deadline — rush jobs require faster turnaround
Special Instructions	Read any notes from the client carefully before starting
Job Type	Standard service, rush, stakeout, registered agent, etc.
Compensation	Your rate for this job is shown on the job detail page

Accepting or Declining a Job

You can accept or decline a job from the job detail screen. Best practices:

• Accept promptly — clients expect a response within a few hours for standard jobs, sooner for rush
• Only accept jobs you can realistically complete by the due date
• If you need to decline, do so quickly so the client can reassign to another server
• Add a note when declining to explain the reason (e.g., outside service area, unavailable)

Rush Jobs Rush jobs are marked with a priority flag and carry a higher rate. They typically have same-day or next-day due dates. Review rush jobs immediately upon notification and respond as soon as possible.

4. Working a Job: Recording Attempts

What is an Attempt?

Every time you go to the service address — whether you successfully serve the documents or not — you must record it as an Attempt in ServeManager. Attempts are the legal record of your work and form the basis of the affidavit.

Recording an Attempt (Mobile App)

The mobile app is the recommended way to record attempts in the field:

1. Open the job from your Jobs list
2. Tap Add Attempt
3. The app automatically captures your GPS location — confirm it is accurate
4. Enter the date and time of the attempt
5. Select the service type from the dropdown
6. If someone was contacted, enter their description (name, age, relationship to recipient)
7. Add any relevant notes about the attempt
8. Optionally attach a photo of the address or any relevant evidence
9. Tap Save Attempt

Recording an Attempt (Web)

If you are entering attempt data after the fact from a desktop:

1. Open the job from your Jobs dashboard
2. Click the Attempts tab
3. Click Add New Attempt
4. Enter all required fields manually (date, time, address, service type, notes)
5. Save the attempt

⚠  Important: Record Attempts in Real Time Always record attempts as close to the actual time of service as possible. GPS coordinates, timestamps, and accurate descriptions are critical for a legally sound affidavit. Retroactively entered attempts may raise questions in court.

Required Information for Each Attempt

Field	Required?	Notes
Date & Time	Required	Must reflect the actual date and time you were at the address
Address	Required	Confirm or correct the service address if different from the job
GPS Coordinates	Required	Captured automatically via mobile app; enter manually if using web
Service Type	Required	Select from the service type dropdown
Recipient Description	If served or contact made	Name, approximate age, relationship to recipient (e.g., “co-resident”)
Notes	Recommended	Any additional details that may be relevant to the affidavit
Photo	Optional	Photo of address, signage, or other evidence

5. Completing a Job

Marking a Job as Served

Once you have successfully served the documents:

1. Open the job in ServeManager
2. Ensure your Attempt is recorded with a “Served” service type and all details filled in
3. The job status will update to Served automatically once a successful attempt is logged

Marking a Job as Non-Served

If you have exhausted all reasonable attempts and service could not be completed:

1. Ensure all attempts are recorded with accurate outcomes and notes
2. Create an attempt and choose the “Non-Service” service type
3. Add a final note summarizing your efforts and the reason service was not possible
4. Save the attempt and share the attempt with the client.

How Many Attempts Are Required? Requirements vary by state and client instructions. Check the job’s special instructions for any client-specific requirements. As a general rule, most jurisdictions expect at least 3 attempts at different times of day before a non-serve is filed. When in doubt, contact the client through the job notes before marking non-served.

Communicating with the Client

You can message the client directly within ServeManager using the job’s Notes section. Use this to:

• Ask clarifying questions before attempting service
• Report difficulties or unusual circumstances
• Request additional attempts beyond the standard number
• Notify the client of delays or issues in real time

To add a note:

1. Open the job
2. Click the Notes tab
3. Type your message and click Save
4. Before saving, select the desired contacts that will receive an email notification of the note. A note can be shared at any time after saved

6. Generating the Affidavit

What is an Affidavit?

The affidavit (also called Proof of Service) is the formal legal document that confirms service was completed. It is generated from your recorded attempt data and must be signed before it is returned to the client. Clients need affidavits to file with courts as evidence of service.

Generating and Signing an Affidavit

1. Open the completed job (status must be Served or Non-Served)
2. Navigate to the Affidavit tab
3. The Agency will create the affidavit, click the affidavit to open the document
4. Review all auto-populated fields carefully:

Auto-Populated Field	Source Data
Recipient name & address	From the job details
Document descriptions	From the documents attached to the job
Attempt dates, times & GPS	From your recorded attempts
Recipient description	From the contact details in your attempt records
Server name & credentials	From your user profile
Court & case information	From the job details provided by the client

1. Correct any errors — if attempt data is wrong, edit the attempt before finalizing
2. Click Sign Affidavit on the signature line to apply your digital signature
3. Once signed, the affidavit is locked and automatically shared with the client
4. Download a copy for your records if needed

⚠  Affidavits Cannot Be Edited After Signing Once an affidavit is electronically signed, it is locked and cannot be modified. Make sure all attempt data, contact descriptions, and dates are accurate before you sign. If an error is found after signing, contact the client and ServeManager support.

Saving your Digital Signature

1. Open the ServeManager App
2. Navigate to the Account tab
3. Press “Add electronic signature”
4. Using your device’s touchscreen, draw your signature to save it to your profile to easily sign/save affidavits from the desktop/app

7. Getting Paid

How Payment Works on ServerHub

ServerHub uses automatic wallet-to-wallet payments powered by Dwolla. When a job is completed and the affidavit is finalized, payment is automatically transferred from the client’s ServeManager Wallet to yours — no manual invoicing or payment requests are needed.

Payment Requirements

To receive payments, your wallet must be fully set up:

Requirement	Status Needed	What to Do If Not Done
Dwolla Wallet Created	Verified	Go to Wallet in your account menu and complete setup
Identity Verified	Verified	Ensure all info matches official documents; resubmit if in retry mode
Bank Account Linked	Connected	Link your bank account via Plaid in the Wallet section
W9 Submitted	On file	Submit your W9 through the Wallet or Settings section

Payment Timing Payments are triggered automatically once the affidavit is signed and the job is marked complete. ACH transfers via Dwolla typically take 1–3 business days to appear in your linked bank account, depending on your bank.

Viewing Your Payment History

You can view all payments received, pending, and failed in your Wallet:

1. Click Wallet in the main navigation menu
2. Your current balance and recent transfers are shown on the Wallet summary page
3. Click on any transfer to see the details, including which job it was for
4. To withdraw your balance to your bank account, click Withdraw and enter the amount

Wallet Transfer Statuses

Status	Meaning	Action Needed
Pending	Transfer sent to Dwolla, awaiting processing	None — typically resolves within 1–3 business days
Processed	Payment complete — funds are in your wallet	None
Queued	Transfer waiting on a requirement (e.g., W9 or NSID)	Check wallet setup; ensure W9 is submitted
Failed	Transfer failed to process	Check your bank account connection; contact support if unresolved
Canceled	Transfer was canceled	Contact [email protected] for details

Wallet Setup: Personal vs. Business

When setting up your Dwolla wallet, you must choose between Personal and Business. This choice cannot be changed once made.

Wallet Type	Best For	Documents Required
Personal	Individual process servers being paid as a person	Government-issued ID, Social Security Number
Business	Agencies managing company funds and paying employees	EIN letter, business formation docs, controller identity info

Critical Wallet Rules Use your full legal name — no nicknames Physical address only — no P.O. boxes Business name must exactly match your IRS documents Wallet type cannot be changed after selection — choose carefully No credit check is performed — this will not affect your credit score

8. Job Status Reference

Understanding job statuses helps you know exactly where a job stands and what action (if any) is needed from you.

Status	Meaning	Your Action
Pending	Job created and assigned to you, awaiting acceptance	Review and accept or decline
In Progress	You have accepted the job and service is underway	Record attempts as you go
Served	Service was completed successfully	Generate and sign the affidavit
Non-Served	All attempts exhausted — service could not be completed	Ensure all attempts are logged; notify client
Affidavit Pending	Awaiting affidavit generation or signature	Open the job and complete the affidavit
Complete	Affidavit signed and returned to client; payment triggered	No action needed
Cancelled	Job was cancelled by the client before completion	No action needed

9. Tips & Best Practices

For Faster, Smoother Jobs

Best Practices for ServeManager Agents Download and read the documents before heading out — know who and what you’re serving Record attempts immediately in the mobile app — do not wait until you get home Always enable GPS — location data on attempts is critical for court-admissible affidavits Take a photo of the address on every attempt, even if unsuccessful Add detailed notes, especially when someone is contacted or refuses service Communicate through the job notes, not by phone or email — all communication is documented Sign affidavits promptly — clients often have court filing deadlines Keep your wallet verified and bank connected to avoid payment delays

Common Mistakes to Avoid

Mistake	Why It Matters	How to Avoid
Recording attempts from memory later	Inaccurate timestamps and GPS undermine the affidavit’s validity in court	Use the mobile app to record attempts in real time at the address
Skipping the person description	Missing contact info weakens the proof of service	Always record name, approximate age, and relationship to recipient when someone is contacted
Signing the affidavit without reviewing	Errors in the affidavit cannot be corrected after signing	Read every field before signing; fix attempt data if anything looks wrong
Not reading special instructions	Clients may require specific handling, number of attempts, or timing	Read the job’s special instructions before starting
Marking non-served too early	Some jurisdictions require a minimum number of attempts	Check client instructions and local rules before marking non-served
Ignoring wallet setup	Payments queue and are not released until wallet is verified	Complete wallet setup before accepting your first job

10. Troubleshooting & Support

Common Issues & Quick Fixes

Issue	Likely Cause	What to Do
Can’t log in	Wrong password or expired invitation link	Use “Forgot Password” on the login page; contact your admin if the invitation link expired
No GPS on mobile app	Location permissions not granted	Go to your phone’s Settings > Apps > ServeManager and enable Location (set to “Always” or “While Using”)
Job not appearing in my dashboard	Job may not have been fully assigned to you	Ask your client to confirm the job was assigned to your account; check all job filters
Affidavit tab not available	Job may not be in Served or Non-Served status	Ensure at least one attempt is recorded with a final outcome before generating the affidavit
Payment not received after completion	Wallet not verified or bank account not linked	Check your Wallet status; ensure identity verification is complete and bank account is connected via Plaid
Wallet stuck in ‘retry’ mode	Identity information mismatch with official docs	Re-enter your details carefully matching legal documents exactly; contact [email protected] if unresolved
Client can’t see my affidavit	Affidavit may not be fully signed	Confirm you completed the electronic signature; a signed affidavit is shared automatically

Support Contacts

Support Type	Contact	For
ServeManager General Support	[email protected]	Account access, job issues, affidavit templates, technical problems
Wallet & Payment Support	[email protected]	Identity verification issues, retry/document mode, payment failures
In-App Help	Help menu in ServeManager	Step-by-step guides, FAQs, and documentation