.webp)
We sell SaaSFrame licenses on Gumroad, a secured online selling platform for creators.
SaaSFrame gets updated all the time! Every new update and version will immediately be made available to all SaaSFrame users.
The licence key required to create your SaaSFrame account is send by Gumroad once you made your purchase. If this email is blocked by your email client, send me an email at antoine[at]unmake[dot]io so I can resend the licence key.
You can generate an invoice on Gumroad once you purchased SaaSFrame. You will find the link in the order confirmation email.
If you're not satisfied, you can ask for a refund within 7 days. Just send me an email at antoine[at]unmake[dot]io
A SaaS inbox organizes incoming work so users can decide what needs attention, who owns it, and what happens next. Messages are only one part of that task. An effective inbox connects queue navigation, conversation context, and clear workflow states.
The SaaSFrame references show personal and collaborative inbox structures. Their visible layouts help explain how density, assignment, and conversation detail can work together without assuming behavior that a screenshot cannot demonstrate.
An inbox can contain customer conversations, notifications, requests, or internal messages. Choose labels that reflect the work rather than using a familiar email metaphor for every kind of object.
The primary queue should answer why an item is present. An assigned conversation, unassigned request, and completed thread require different attention. Keep those distinctions available without forcing users to inspect every message.
Before deciding on columns or cards, define the state changes that matter. The layout should express that model consistently in navigation, rows, and the detail view.
The Front reference uses a three-part structure: inbox navigation, a conversation list, and an open message. The list remains visible while the selected thread provides reading and response context.
This supports movement through a queue without repeatedly leaving the working surface. The cost is competition for horizontal space. Give each region a specific job and avoid showing every available metadata field in every column.
A selected row needs a clear visual state. Users should be able to connect the open conversation to its position in the list, especially after scrolling or changing filters.
The Fernand capture presents a compact inbox with routes for waiting-for-answer and broader conversation access. A small list of initial conversations leaves the main surface relatively sparse.
State labels can describe responsibility better than a simple read/unread split. A read message may still need action, while an unread item may belong to another teammate. Choose states that help users decide what to do.
Keep the meaning stable. If a waiting state depends on the last sender, make that rule understandable. If it depends on an explicit user action, show the action that moves the conversation there.
The second Front capture shows queue states such as open, later, and done alongside a selected support conversation. The detail header includes an assignee and an open status, while the conversation contains a visible summary and customer message.
These elements connect the content to the workflow. A reader can see both the issue and its current owner. An assignment control is most useful when its scope is clear: assigning a whole conversation differs from mentioning someone in a reply.
If summaries are generated or abbreviated, preserve access to the underlying messages. A concise overview can support triage but should not become the only available account of the conversation.
Collaborative inboxes often support both external responses and internal comments. Make the active composition mode obvious before a user starts typing and keep it visible near submission.
Use distinct labels, recipient context, and appropriate visual treatment. The consequence of choosing the wrong mode is too significant to depend on a subtle color change alone.
After submission, show the actual result. A posted internal note, queued reply, and delivered response are different states. Do not imply delivery when the system only accepted a request.
A row may need sender, subject, preview, timestamp, ownership, and priority. Select the combination that supports the most common decisions in the queue.
Keep ordering and grouping understandable. Newest-first is useful for recent activity; priority ordering can support urgent work but needs clear criteria. Show the active sorting or filtering context.
Use badges sparingly. When every row has several prominent indicators, the interface stops distinguishing the information that actually changes the next action.
Search, filters, and inbox navigation can produce similar-looking lists with different meanings. Keep the active scope visible and provide a clear route back to the original queue.
If a conversation disappears after a status change, explain the outcome or provide a sensible next selection. Sudden disappearance without feedback can look like data loss.
Treat an empty filtered result differently from an empty inbox. One means the query found no matches; the other may indicate that all current work is handled or that setup is incomplete.
A shared inbox needs understandable ownership and handoff. Make it possible to see whether work is unassigned, owned by the current user, or assigned elsewhere without exposing unnecessary complexity.
Review simultaneous work and stale state. A static screenshot cannot show whether another teammate is replying or changing ownership. The implementation needs appropriate feedback when those changes affect the current task.
Keep permission-dependent actions coherent. A user who can read a conversation but cannot reassign it should understand the available route to request a handoff.
On smaller screens, a three-column inbox may become a sequence of views. Preserve the selected queue and list position when users return from the conversation.
Keyboard navigation, focus, and clear control labels matter in a high-frequency workspace. Check how users move through rows, open a thread, switch composition mode, and return to the list.
Avoid relying only on icons or color for ownership and state. Dense layouts need explicit meaning just as much as sparse ones.
Evaluate whether users can identify the next item, understand responsibility, and complete or defer work with confidence. A fast reply is not necessarily a resolved issue.
Test a new conversation, a long thread, unassigned work, a handoff, an empty search, and a conversation that changes while open. Those cases reveal how well the queue model survives real use.
Explore SaaSFrame's inbox references to compare list density and workflow visibility. Borrow structures that match your team's responsibility model rather than copying a mail layout by default.
No. Three columns keep queue and detail context together, but a smaller screen or simpler task may work better with sequential views that preserve position.
No. Reading describes attention to content; resolution describes workflow progress. Keep both concepts distinct when they matter to the product.
Place current ownership near the active conversation and expose enough information in the list for triage. Make reassignment distinguishable from a mention or internal comment.
