• 0
    Assign Custom Fields to Circles
    6 months agoopen0
    I'd like the ability to assign custom fields to Circles, so a custom field would only be visible in a client's record if the client is a member of the circle assigned to the field. This would make it possible to use different custom fields for different types of clients, without fields cluttering up the client record when they're not applicable to that client.Additionally, I'd like to be able to associate a form with one or more Circles, so when a client submits a lead form for a specific service, it would automatically add the client to the Circle or Circles pertaining to that service. When adding custom fields to a form, it would only make available the generic custom fields plus any fields associated with the selected Circle. Any fields associated with other Circles would not show up in the custom field selection list.For example, suppose you're a real estate agent who handles both residential and commercial real estate. On the lead intake form, the data you need to collect for a residential client would be completely different from the data that you'd collect from a commercial client. In this example, we'd assign all the residential fields to one circle and all the commercial fields to a different circle. Then, we could create separate intake forms for each. When creating the form, we'd assign it to either the residential or commercial Circle and it would make available the fields corresponding to its assigned Circle. Finally, in residential client records, all the commercial fields would be hidden and vice versa.
  • 3
    HTTP Request Flow Action
    7 months agoopen0
    I know that other users have requested web hooks, but I'd like to take it a step further.I propose adding a new Flow action called "HTTP Request". This would send data to an external API, then receive a response from the API and update the client record with the received data. To configure the action, you'd enter the URL you want to call, along with the fields you want to pass to the URL.The action would submit the HTTP request, either as a GET, POST or JSON POST (configurable). It would then receive the response as a JSON object and update the client record with the data contained in the JSON object.For example, suppose you want to link a SuiteDash client record to a corresponding client record in an external database. The purpose would be to allow the client to view data from the external database on a custom page within his SuiteDash portal.With this Flow action, we could submit an "Add Client" request to the external application. The external application would create the client record and pass back the customer ID and a secret key in the response JSON. These would be stored in custom fields in the client record.In the custom portal page, we'd add an iFrame that uses Dynamic Data Placeholders to insert the customer ID and secret key for that client into the iFrame URL query string. This would then log the user into the external application and display the application inside the iFrame. Alternatively, you could use Javascript to render the external application directly to the portal page, without using an iFrame.This would allow SuiteDash to integrate with any custom application, displaying the application in a SuiteDash portal page.
  • 13
    Modernize UI/UX
    7 months agoopen0
    In terms of its feature set, SuiteDash is the most comprehensive business management tool I’ve ever seen. Unfortunately, the UI/UX is extremely dated.Most actions require a full page reload, which is slow and inefficient. The themes also look old fashioned. Mr Clean is the most modern-looking theme, but even that theme looks dated. The entire platform needs to be re-implemented on a modern UI framework like React or Angular.I’d also like to mention that the responsive mobile UI is quite buggy. It doesn’t seem like a desktop UI that was adapted to mobile, rather than a mobile-first UI, that all modern apps are built for. For example, on many mobile pages, it’s possible to scroll horizontally, revealing a huge empty space to the right of the content. This shouldn’t happen and it looks unprofessional.
  • 5
    Telegram and Slack Integration
    7 months agoopen0
    The biggest weakness of SuiteDash is that it’s isolated from native desktop and mobile apps, requiring users to login to the web app to receive notifications and communicate with staff members and clients. This is inefficient and inconvenient.I understand that due to the white labeling feature, it’s not possible to create a native SuiteDash mobile app. The solution is to integrate with Telegram and Slack. It’s easy to create a Telegram bot, so each company could have its own bot. The bot would enable users to receive notifications, manage projects and tasks and communicate with staff members and clients using a native desktop or mobile app.To get an idea of how this could work, check out Re: plain, which is a website live support chat that’s built entirely on Telegram. It doesn’t even have a web UI, because all functions take place inside of Telegram. I’m certainly not suggesting that you abandon your web UI, but you could easily create a Telegram and Slack UI that would duplicate most or all of the web functionality within these native apps.
  • 11
    Custom Database Tables
    7 months agoopen1
    Currently, SuiteDash is limited to using only its predefined tables, like contacts, events, deals, invoices, etc... We can create custom fields within each table, but imagine the power of being able to create custom tables to store any type of data. This would be the ultimate in flexibility, as it would allow us to use SuiteDash to create industry-specific applications.Custom tables would function similarly to the built-in tables, except all the fields would be custom fields, you could create as many custom tables as you want, and you could link them together using key fields. The data stored in custom tables would be visible to staff members via a tab in the CRM.On the client side, we could specify which tables are visible to clients and SuiteDash would automatically create a page for each table, displaying the data in a grid format, with one row for each record. When a client clicks on a row, it would open the detailed view for that row either in a new page or in an overlay. We should be able to specify which fields will appear in the grid and which fields will appear in the detail view. We could optionally give clients the ability to edit their records , delete records, or create new records, either from within SuiteDash or from an external form or widget.For example, suppose you're a real estate agent and you have property listings on your website. Each listing could have a "Favorite" button that would be created by embed code generated by SuiteDash. When a user clicks on the Favorite button, it would automatically add the information for that property to his "My Properties" table in SuiteDash. If he doesn't have a SuiteDash account, it would prompt him to create an account the first time he clicks on the button. He could then login to SuiteDash and view all the properties he favorited and remove any ones he no longer wants. Your staff members could receive notifications when clients favorite properties and view the properties each client has favorited.
  • 2
    Automatically Lookup Client Info
    7 months agoopen0
    Automatically fetch a default profile photo for each new client from Gravatar. Also integrate with third party APIs that automatically lookup biographical information for each new client.
  • 1
    HelpWise Integration
    7 months agoopen0
    HelpWise is an advanced email-based support system. It essentially allows you to create shared inboxes, so when customers email support@yourcompany.com, whichever staff members you designate can respond to the inquiry and everyone can see what's happening with each customer. Besides email, it also supports shared inboxes for Facebook, Twitter, SMS and it includes a live support chat widget for your website.I know SuiteDash is working on its own support ticket system, but it's a conventional system, not a shared inbox type system like what HelpWise offers and it doesn't support alternate channels like Facebook, Twiiter, SMS, website chat, etc... it would be great if you could integrate with HelpWise so that HelpWise communications could automatically flow into the CRM and could synchronize with your forthcoming support ticket system.