Documentation · 5 / 12
Requests: how the two sides meet
One form for companies and providers, a reference number and an answer by e-mail.
For companies
The contact form asks for company, name, e-mail and a description of the work, plus the services needed. After sending you get a reference number. The team reads the request and answers by e-mail with matching providers.
For providers
Providers use the same form in the role of service provider. On a project page the button for providers carries the project number into the form.
Protection against misuse
The form has a captcha, a hidden trap field for bots and a limit on the number of requests per address.
What happens inside
Each request lands in the request list of the team. From there it can be turned into a project in the workspace.
Use cases
Ask for a SOC provider
- Open Contact.
- Describe the systems, the size and the timing.
- Tick the service areas.
- Send the form and keep the reference number.
- Answer the e-mail from the team.
Answer a project as a provider
- Open the project.
- Press the button for providers.
- Add your company and your services.
- Send the form.
User stories
- As a company, I want to describe my need once, so that I do not have to brief ten providers.
- As a provider, I want to answer one specific project, so that my offer is on point.
- As a team member, I want every request in one list, so that nothing is lost.
Updated: