Help Center

Answers,
guides and a human when you need one.

Most questions are answered by a five-minute guide. When they aren't, a real engineer replies — not a script.

Getting started

The fastest path to a useful company brain is three sources: where you talk, where you write and where you track work.

  • Connect your first source in under two minutes
  • Scope a source to specific channels, folders or projects
  • Invite teammates and mirror existing tool permissions
  • Read your first generated insight

Investor updates

Publish periodic updates and control exactly what each investor can open — reports only, reports plus metrics, or the whole workspace read-only.

  • Invite investors by type: Solo, Angel, Syndicate, VC, Accelerator, Family Office
  • Change an investor's access level at any time
  • Track opens, last viewed and engagement per update

Response times

Pro Team gets a 24-hour first response on business days. Startup gets four hours. Enterprise adds a named success manager and an on-call escalation path.

Troubleshooting

If a source stops syncing, the connector card shows the exact failure and a one-click reconnect. Historical data is never lost during a disconnect.

Response, measured

Support numbers we publish whether they flatter us or not.

Rolling 90-day figures, recalculated weekly from the same workspace you would be writing into.

41

0 min

Median first response

During 07:00-21:00 UTC, every working day.

94

0%

Resolved without escalation

The first person who replies usually finishes the job.

1

0

Business day for security reviews

Questionnaires, DPAs and procurement forms included.

4.8

0.0/5

Satisfaction

Rated on resolution, not on politeness.

01

Where support requests actually come from

Most of what reaches us is about connecting a source or shaping permissions, which is why those two areas get the most engineering attention. Product bugs are a small and shrinking slice.

  • Connection and permission questions dominate week one
  • Volume per workspace drops sharply after the first month
  • Every ticket links back to the workspace state that produced it

Requests by topic

Last 90 days.

  • Connecting a source148
  • Permissions & access96
  • Billing61
  • Feature guidance54
  • Bugs22

Tickets per workspace, by week

Support load falls as the graph fills in.

1.1
Tickets

What happens next

The path a request takes after you send it.

You write, we read context first

Your message arrives attached to your workspace's state, so nobody asks you to re-describe your setup or send screenshots of settings.

Median 41 minutes to first reply

A human who can fix it replies

Support at Loreflow is staffed by people with commit access. There is no tier-one script and no ticket ping-pong.

94% resolved without escalation

Fixes ship, and you hear about it

If the answer is a product change, it goes on the changelog and we come back to you with the release note.

Weekly release cadence

Coverage

When someone is awake.

Support hours mapped against the days and hours requests actually arrive.

Request density

By weekday and hour block.

Mon
Tue
Wed
Thu
Fri

Channel mix

How teams prefer to reach us.

381requests
  • In-app52
  • Email27
  • Shared Slack16
  • Call5

Have a question that is not really support?

Security reviews, procurement, migrations and 'will this work for us' calls all go through the same inbox.

FAQ

About support.

Response times and escalation.

Open the live demo

Within one business day on every plan, and same-day for anything blocking a connector or a sync.

Include the workspace name and the connector involved. Sync issues are usually diagnosed from the connector status alone.

Yes. We will walk through connector selection and the first context map review with your team at no cost.