Skip to content

General Feedback

You have ideas, and we want to hear them! Share your stories to help us create a product that best fits your needs. The best requests aren’t just the request, but the reason behind the request. So don’t be shy and share your story behind why this would be valuable and how you would use it. Your story has the power to garner votes from other users as well.

We will be responding to the requests on this board to give definitive answers or to get a better understanding of the request. And while we do take our client feedback seriously, we won’t be able to promise all of the requested features will be added to Classy. Separately, if you are interested in participating in product research, we'd love to hear from you

Additional information about posting an idea

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

216 results found

  1. Remove Functionality for Campaign Creation of Fundraising Pages/Teams in Salesforce

    I understand that a Classy Campaign gets created in SF as the Parent Campaign, then a Fundraising Team Page as a child of that Parent Campaign, and then an Individual Fundraising page as the grandchild of the Parent Campaign.

    We would love to remove this functionality as we just want donations flowing to the main parent campaign and do not have a need for these children and grandchildren campaigns. This creates extra work for us in deleting these campaigns as they come in.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Assign Organization to Recurring Donation when made with Company Credit Card in Salesforce

    When a donor with a company selects "Is a company credit card" at checkout, I would expect the Organization account matched to/created in Salesforce to be the primary donor/rollup on the Classy Recurring Profile and the NPSP Recurring Donation Object for Account.

    This functionality would improve our ability to report company recurring donations in Salesforce

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Create a setting in Classy Control Panel within Salesforce to update email address on Contact

    If an email address is updated on the Supporter profile in Classy, that email address is updated on the Classy Supporter record in Salesforce, but not on the Contact record. Currently, the integration only writes to the Contact email field if the field is blank. Changing that logic to write to the field when an update from Classy happens would improve accuracy between Classy and Salesforce for organizations. Creating a setting in the Classy Control Panel Account & Contact settings would place ownership on these changes updating data on the Contact object with the orgs. This setting will also be…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow Duplicate Creation for C4SF

    We want to create a duplicate Contact record in Salesforce if our rule has "Allow On Creation = Allow" to ensure all donations are created in real time, regardless of duplicates

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Sync Close Reason for Recurring Plans

    The revenue analytics team has historically done reporting on the reasons that recurring giving plans close, but since moving our recurring giving plans to Classy, that information no longer exists within Salesforce. I see that in Classy there is a field “Reason provided by admin” that is sometimes filled out. Could we get this field to sync into the Salesforce field CloseReasonDescription__c on the Recurring Donation object associated with each Classy recurring giving plan?

    Another reason that recurring giving plans “close” is that they are suspended after 3 months of unsuccessful transactions. There is no indication in Salesforce…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. classy_npsp:Too many query rows: 50001

    The following error is ocurring with Classy for Salesforce:

    Failed to process batch for class 'stayclassy.ClassyApiFetchRequestBatch' for job id '707Nr000003qiHz'

    caused by: System.LimitException: classy_npsp:Too many query rows: 50001

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Company Donations should add info besides name to Organizational Accounts in Salesforce

    Currently, the integration only matches to and creates the Name of an Organizational account when a company credit card is used in Classy. We would like to see things such as the billing address be used to match and or create Organizational Accounts.

    As using name only is a huge limitation for Account matching and creation, causing duplicates and inaccurate records.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Investigating using the Company Name and Billing Address on checkout with company credit card flow to be used for organization match into Salesforce.

  8. No changes to Salesforce field values without Custom Mapping option

    Do not change any existing Salesforce field without an option to map to client instance values. .
    Changing client Salesforce instance values can and does trigger negative downstream consequences that are unpredictable, especially without a testing environment..

    Classy has plenty of "stayclassy__" fields to update and could add more if necessary.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add the Campaign ID to the Payout Endpoint of the API

    The API we’re building already has many ‘workarounds’ by making other calls for data to the point where it’s impacting the API’s performance. It would be helpful to have Campaign ID included in the Payout Endpoint via the API

    The Salvation Army has expressed that they really need this parameter.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Default Double the Donation Stage Field

    Double the donation transactions get pushed through to our
    Salesforce opportunity record as Closed Won in the stage field. I'm wondering if there is
    something else that can be used instead of Closed Won for transactions like
    these? By something else, I was thinking of "Posted" that would show up in
    the stage field. That is one of the choices in the drop down stage field
    in the opportunity record in Salesforce. I know there's three apps trying
    to work together (Classy, Dtd, Salesforce). The Dtd transactions
    technically are not Closed Won--at least as we use Closed Won--at the time…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add option to update most recent duplicate record instead of adding another duplicate record.

    When multiple duplicates are detected with the Salesforce integration, Classy simple adds an additional contact which creates MORE duplicates. It would be great to have an option to simply update the most recently created record instead of creating a new duplicate.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Chariot Integration

    Met the creators of Chariot https://www.givechariot.com/ at the Bridge Conference last week and their DAF tool is absolutely incredible. They are able to integrate into solutions like Classy and I'd like to advocate Classy integrate with Chariot so we can integrate DAF into our payment solutions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Sync Fundraising Commitment information to Salesforce

    Within Classy, campaigns have a "Commitment Management" tab that lists information about a fundraiser and the fundraising commitment they signed up for. These fields include: fundraiser name, fundraising page ID, ticket name, commitment amount, commitment remaining, status and deadline.

    Request for this information to sync over to Salesforce on the fundraising page's campaign so these fundraising commitment details can be tracked and reported on from Salesforce.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 'Create fundraising page' via API

    Update API to include 'create fundraising page' action to allow more flexibility to leverage Classy in alternative workflows.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Pledge Salesforce

    Would like the ability for Pledges (from Classy Live) to sync to Salesforce, and then for Salesforce to update accordingly and for Salesforce to turn the pledge opportunity into a transaction once the transaction goes through. But ultimately would like visibility into that Pledge in Salesforce vs. only Classy Live (even pre-transaction).

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Ability to Disable/Customize Campaign Member Statuses

    Organizations would sometimes like to prevent certain campaign member statuses from generating in Salesforce, like Team Captain or Fundraiser, or to be able to change the text label of these statuses and have the C4SF integration map to them.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Customize soft credits for fundraisers and team captains

    Allow admins to customize whether team captains get soft credits or not. Allow admins to use custom credits for team captains. Currently there is no way to distinguish in Salesforce between funds donated to a team captain's team member or the captain's individual fundraising page as a soft credit is given for both. Previously Team captains did not receive a soft credit. Allow admins to customize between these options.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. I would love it if you would suggest the possibility to add a connection to both Sandbox AND Production for Salesforce.

    Add a connection to both Sandbox AND Production for Salesforce not just one. Make the migration from Sandbox to Production easier. We have been using Classy and prepping SF with the connection to Sandbox. Now that we are migrating from Sandbox to Prod we will have duplicate campaigns and funds because we can't change the classy campaign and designation to the prod campaign and designation. Classy will create a brand new.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. When using Classy for NPSP, allow recurring plan opportunities to inherit plan's GAU allocation(s)

    Current functionality for organizations using the Classy for NPSP package with Recurring Donations + GAU Allocations enabled in the Classy Control Panel, the integration will set the opportunity's GAU allocation based on the Program Designation associated with the transaction in Classy Manager.

    NPSP has functionality for opportunities created under a Recurring Donation to receive the Recurring Donation's allocation. For example, if an NPSP Recurring Donation is created in Salesforce with 2 GAU Allocations for 50% for each GAU, NPSP functionality would be to create 2 50% GAU allocations on the opportunities under that Recurring Donation record, but when using Classy…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 10 11
  • Don't see your idea?

Feedback and Knowledge Base