Formimp is a private application built for Greg Hluska Consulting. It delivers contact and support messages from websites and applications into the communication tools where support work actually happens.
In Siteimp, Formimp is used to send in-app support requests to a Siteimp support channel. Instead of dropping support messages into a hidden inbox or a one-off form system, Formimp puts them where they can become conversations, follow-up questions, bug reports, documentation improvements, and product polish tasks.
The idea is simple: a support request should not disappear into a silo. It should land somewhere useful.
What Formimp does
Formimp accepts a message from a form and delivers it to a configured team communication channel.
Depending on the project, that channel may be in:
- Slack
- Discord
For Siteimp support, Formimp is used as the delivery layer between the app and the support channel. Siteimp prepares the support report. Formimp sends it to the channel where the Siteimp team can read it and follow up.
Formimp is not a public form-builder product. It is a private internal tool used to make contact and support messages easier to handle.
Why Siteimp uses Formimp
Siteimp uses Formimp because support works better when messages reach the place where the team already communicates.
A traditional support form can be too isolated. Someone fills out a form, the message lands in a mailbox or database, and then the support conversation has to be recreated somewhere else.
Formimp skips that extra isolation layer. It lets a support request arrive in a team channel where it can be discussed, assigned, answered, and turned into follow-up work.
That helps Siteimp support in a few ways:
- support requests are visible quickly
- problems can become team conversations
- confusing issues can become documentation tasks
- repeated issues can become product improvements
- bug reports can be discussed without copying messages between tools
- follow-up can happen from the same context as the original request
The goal is not just to receive a form submission. The goal is to make the message useful.
How Formimp fits into Siteimp support
When you send a support request from Siteimp, the support flow has a few parts.
- You open the Help Drawer.
- You choose Contact tech support.
- You describe the problem.
- You choose how Siteimp support should contact you.
- You may run diagnostics and decide whether to include them.
- You review the final report.
- Siteimp sends the approved report through Formimp.
- Formimp delivers the request to the Siteimp support channel.
Formimp handles the delivery step. It does not decide what you write, what diagnostics you include, or whether you send the request. Those choices happen inside Siteimp before the message is submitted.
What gets sent through Formimp
Formimp sends the support report that Siteimp prepares.
A Siteimp support report may include:
- your description of what you were trying to do
- what happened
- what you expected to happen
- urgency or deadline details you entered
- your name and email address, if provided
- contact instructions, if provided
- basic app context, if enabled
- diagnostics, if you ran them and chose to include them
Before sending, Siteimp shows you the report so you can review what will be included.
What Formimp does not do
Formimp is intentionally narrow.
Formimp does not:
- scrape your computer
- collect unrelated files
- collect browser history
- collect passwords
- attach full app logs by default
- decide which diagnostics to include
- replace the Siteimp Help Drawer
- replace direct follow-up from support
It is a delivery tool. Siteimp builds the support report, and Formimp sends the report to the configured support channel.
Why Slack or Discord?
Slack and Discord are useful for support because they make messages easy to see, discuss, and act on.
A support request in a communication channel can quickly become:
- a reply to the user
- a clarification question
- a bug report
- a documentation improvement
- a design polish note
- a feature refinement
- a future support article
That matters for Siteimp because support is not only about fixing one request. It is also a way to notice where the product is confusing, where documentation is thin, and where the app can explain itself better.
In practice, a good support message can improve the product for the next user.
Privacy and third-party services
Because Formimp delivers messages to Slack or Discord channels, support messages sent through Formimp may be processed by those third-party services.
That means users who send support requests through Siteimp are also subject to the privacy policies and data practices of the destination service used for the support channel.
For Siteimp, the practical tradeoff is visibility and better support follow-up. Instead of support messages being trapped in a private form database, they arrive inside the communication tools where support work can happen.
This does not mean Siteimp should send more information than needed. The support flow is designed around review and consent:
- you write the problem description
- you choose whether to include basic app context
- you can run diagnostics before including them
- you can review the final report before sending
- diagnostics are optional
- logs are not attached to the standard support request
The aim is to keep support useful without making the request feel mysterious.
Why support requests should become conversations
Some support systems treat a form submission as the end of the user's work and the start of a ticket queue.
Siteimp takes a different view. A support request is often the start of a conversation.
That conversation might reveal:
- a confusing screen
- a missing support article
- a weak error message
- a real bug
- an unclear workflow
- an assumption that did not survive contact with real use
When a request lands in the team communication channel, it is easier to discuss what happened and decide what should change.
This is especially valuable during beta and early releases, when support is one of the fastest ways to learn what the product needs next.
How Formimp helps Siteimp improve
Formimp supports a feedback loop.
A user sends a support request. The request appears in the support channel. The team can answer the user, discuss the cause, and decide whether the issue should turn into a product change.
That can lead to:
- clearer Help Drawer articles
- better in-app explanations
- improved diagnostics
- more helpful error messages
- smoother workflows
- bug fixes
- new support website articles
This is why Formimp is not only a delivery mechanism. It helps support become a product improvement system.
How this differs from ordinary contact forms
A normal contact form usually focuses on submission.
Formimp focuses on delivery into the right working context.
That difference matters. A message in a form database may be technically received, but it is easy for it to become detached from the team's daily work. A message in a support channel can be read, discussed, and turned into action.
For Siteimp, that is the important part. The support request should reach the place where someone can do something useful with it.
How this relates to the Help Drawer
The Help Drawer and Formimp work together.
The Help Drawer gives screen-specific help first. If the article solves the problem, no support request is needed. If the article is not enough, the support form opens from the same drawer.
Formimp then delivers the reviewed support report.
That creates a support path with three layers:
- Read the relevant help article.
- Send a reviewed support report if you still need help.
- Turn the request into a conversation and product improvement opportunity.
This keeps support close to the app without making the app feel like it is secretly collecting information.
What happens after Formimp delivers a request
After Formimp delivers a support request, Siteimp shows a confirmation and a support request ID.
The request ID is useful if you need to refer to the request later. It also helps connect follow-up conversations to the original support report.
Once the request is sent, the Help Drawer returns to the support article for the current screen. This keeps help available and prevents the completed support form from lingering after submission.
If delivery fails
If the request cannot be delivered, Siteimp keeps the report available so you can copy it and send it by email.
This fallback is important. A support tool should not lose the message you just wrote because the delivery layer failed.
If delivery fails:
- Review the error shown in Siteimp.
- Use Copy report.
- Email the copied report to Siteimp support.
- Include any extra context that may help.
The support request is still useful even when the automatic delivery path fails.
Where to go next
To learn more about Siteimp's support system, read:
- Using the Help Drawer for screen-specific in-app help
- Contacting Siteimp support for the full support request flow
- In-app support articles for the website copy of Siteimp's in-app help
Formimp is intentionally simple. It helps support requests land in the right place, where they can become conversations, fixes, documentation, and a better Siteimp.