Contact

Start in the product. Write when you need a person.

You do not need a call before creating an agency. When a migration, security review, or product question needs context, email goes to the team directly.

  • No sales call before setup
  • No card required to begin
  • Direct email instead of a contact form
  • Security and migration questions get their own path
Choose a route

Put the question in the right lane.

Each link opens your email client with a useful subject. Nothing is submitted until you choose to send it.

Product and account help

Ask about sign-in, agency setup, the first referral, staff access, or something that is blocking current work.

Migration questions

Describe the system or files you are leaving and the size of the active caseload. Do not attach real child data to the first email.

Security and privacy review

Send a vendor questionnaire, data-handling question, or request for the current trust materials.

Everything else

Write directly if your question does not fit one of the paths above. A plain subject line is enough.
Before you write

A little context makes the answer useful.

The first note can stay short. Name the goal, where you are stuck, and the part of the agency affected.

For product help

Include the page name, what you expected, and what happened instead. A screenshot is useful if it contains no protected information.

For migration

Name the current source, approximate active caseload, staff count, and the date you want the new process to begin.

For security

Attach the questionnaire or list the controls your agency must verify. Leave child and family information out of the message.
Self-serve first

Many questions are faster to answer inside the product.

The help center explains core workflows. A free agency lets you test setup and the child record without waiting for a reply.

Read the help center

Use the public guides for setup, records, roles, and the day-to-day product flow.

Test with fictional data

Create the agency and add a fictional referral. You can inspect the workflow before discussing a rollout.
Direct contact

hello@tinysolutions.app

Use a direct note when the product, docs, or migration guide does not answer the question.

Email is for account and business context only. Do not send protected health information.