Fundraising seeks the ability to send an email (and not a banner) incorporating messaging along the lines of: you are an existing donor at ex: $2/month and we are making a call to action to modify existing gift ex: can you make it $2.25? User selects yes/no and we update their recurring monthly amount thereafter.
Alternatively, WMF would provide a form where there are a few buttons with varying amounts that the donor could select from. In either case the EXISTING token is updated and the billing recurs at the new recurring rate.
Note for consideration: How would this handshake with Acoustic to reflect the donors' new updated amount?

• What fields need to be added in Acoustic or Civi to reflect these new actions within that database. (Is the latest current "native amount" the recurring amount? Do we need new fields to show the new amount?)

As per Evelyn's last point, it'd be great to confirm if the current Acoustic field 'AF_latest_native_amount' reflects the recurring amount for active recurring donors, or if there's an additional field required. Also, is there a way for us to check on Acoustic or Civi for those recurring cancellations that were due to their card expiring? Thanks

Adding Mariana's/Fundraising's desired workflow here:

Thanks Evelyn! Noting that the above workflow is a draft open for discussion with fr-tech and other teams involved.

This work would probably be needed for us to enable this functionality: https://phabricator.wikimedia.org/T333182

• What fields need to be added in Acoustic or Civi to reflect these new actions within that database. (Is the latest current "native amount" the recurring amount? Do we need new fields to show the new amount?)

We would likely just update the existing (native) amount field in civicrm_contribution_recur. The previous amount should still be visible in the contact's change log. Then we could also add either a contact tag or an activity to indicate that the contact has upgraded their recurring amount.

Noting that more context has been documented here.

Adding a note in case in helps: initially, the recurring upsell will be mainly targeting the U.S. so we will work on recurring upgrades for this market first.

Questions for stakeholders:

• Is it OK to have just one configurable expiry time for email prefs links and monthly upgrade links, or do the monthly upgrade links need to have their own different configurable lifespan?
• What should show up on the form to upgrade the donation? Donor name? Email? Language selector? Current amount?
• Should there just be one button to confirm the increased amount? And does that amount come from the link or from a pre-set formula?
• If the amount comes from the link, what kind of validation does it need? Should we let clever donors use the form to reduce their donation amount? Probably not below the minimum, at least.
• When a contact has multiple active recurrings, can we just show the highest value one?
• Where should donors go when they click the upgrade button - the normal TY page?

Thanks @Ejegg -- Anil and I just talked about these questions, and we have some initial direction but I'll run it by the team to confirm that what we see as the overall direction is good.

Some answers at https://docs.google.com/document/d/1I271yfASDbP0QXWlEVwlZynEIR28sXvGDqavIUyUfD8/edit?hl=en

This is the last updated flow with the details from the last calls:
https://docs.google.com/presentation/d/1zmLjWW38EfudJEtQYooayjQJICRnossBjuiJmrigQnQ/edit#slide=id.g1dd5ef47764_0_1
And this is the notes doc for the landing upgrade page and the TY pages
https://docs.google.com/document/d/1o1O6SSl05LD5NvIjrgOOHcFp0mi5gW9ak89iQOcisTE/edit#

Flagging DR would like the opportunity to test this before we start using it in campaign.

Adding some context: currently DR enables manual workflows to upgrade supporters https://collab.wikimedia.org/wiki/Fundraising/Donor_Services_Documentation/Advanced_Workflows#Cancelling_&_Updating_Recurring_Donations - part of what we'd like to discover is whether this tool (or preferably a backend version of this in Civi) can help improve these workflows.