It is time consuming (and we often hit the 1000 "collection size limit") to have to map the same custom answers for each campaign (ex: contact information for attendees in ticketed events, phone numbers, title, birthdate, etc). I would like to see these as standard questions that we only have to map a single time in the Classy Custom Field Mapping object in NPSP.

Admin likes the idea of the Classy Live text-to-donate feature, and would like to have this feature available for standard Classy campaigns as well.

Put restrictions on names entered that come into Salesforce. i.e, preventing the name if a donor types “@” or “.com” in their name

Currently, the Classy for NPSP package only maps to a small amount of NPSP fields available to the customer in Salesforce. Larkin Street Youth Services is looking to map certain amounts from Classy to NPSP fields. Specifically, the NPSP "Fair Market Value" field. Additionally, the Classy Custom Field Mapping tool cannot be utilized because the NPSP field types do not match the Classy field types.

have salesforce email campaign ID's associated to Classy campaigns. When the opportunity hits salesforce automate the process where the donation is associated to that salesforce campaign ID

We'd like to capability to remove synced SF transactions from the Failed Sync Dash upon successful transaction.

Save the value of the full URL string that a donor's web browser uses to get to a donation page. Save it on the transaction record. Make it available on the transaction detail page and in transaction reports. Also, have it flow into Salesforce via Classy for Salesforce (E.g., store the values in an Opportunity object field).

Include all parts, including the query string and fragment (even though a fragment is likely not used).

The "AggregateDonationTotals" job that populates data into the "Number of Recurring Donations" field on a Contact record has been depreciated. Although the Classy Recurring Donation record and NPSP Recurring Donation record report on this information, it does not surface on the Contact record. Requesting for this job to be fixed so that this field can be used on the Contact again.

it would be great to have a "Classy Pay for Quickbooks" that would automatically send all Classy Pay payments to Quickbooks, with line item detail for each donation, including donor name, amount, date of donation, campaign, and date of Classy Pay payment/deposit.

Currently, we manually enter our offline/check donations into the Classy campaign. We use Hubspot with Quickbooks integration for invoicing and receiving payments. It would be helpful if when we receive a check payment/donation as long as we used the corresponding Classy campaign ID if it would automatically be entered into Classy. Otherwise, we are doubling up that donation in our CRM.

Would like the ability to send refunds for transactions from CRM to Classy via the open API.

The customer would like to see the C4SF integration enforce Salesforce's hard limit for fields. An example is there 40 character limit in the 'City' field on the donor form. C4SF allows the data to be sent to SF even though it is over the limit for SF.

It would be very helpful for the API to surface when a dedication recipient opened/ interacted with the dedication email.

Admins would like email notifications when an update/new version is released.

Right now, the donor designation overrides all other designations. So, if someone is both a donor & team captain, the donor designation will override team captain. Can organizations have the ability to adjust or edit this?

it would be great to have a Quickbooks integration that would automatically send all Classy Pay payments to Quickbooks, with line item detail for each donation, including donor name, amount, date of donation, campaign.

It'd be nice to be able to add campaigns to Google Event Experience.

Ability to utilize Classy API to pull additional info from campaigns, including event times, location, and hero image.

When utilizing the Classy for Salesforce integration, this team would like the automatic tax receipt sent to donors to be linked as an attachment on the Salesforce opportunity.

Can Classy work with Kindful to help address a few issues with the Kindful/Classy integration:

-ACH transactions show up as Credit Card transactions
-Recurring donations show up as one-time gifts
-Billing Name doesn't map over if different from Supporter Name