BGP Communities to influence default route selection

Has anyone done multiple default route advertisement via bgp using extended BGP communities to influence where each remote site routes? Reason being we have a couple of DC sites with internet connections that we want to route certain sites to each (Dependant on location)

The MPLS provider has said we could use a extended community for each site and then advertise out each community with the default route from each DC, and failover if the other isn't available.

Just trying to work out what that would look like from a config perspective? Want to advertise each main DCs subnets out in addition to influencing the default route fore remote WAN sites.

ISP Router

router bgp 65500

 address-family ipv4 vrf ft-160

  network 172.29.0.64 mask 255.255.255.245

  neighbor 172.29.0.68/29 remote-as 65510

  neighbor 172.29.0.68/29 description Y00x

  neighbor 172.29.0.68/29 activate

  neighbor 172.29.0.68/29 send-community both

  neighbor 172.29.0.68/29 timers 10 30

  maximum-prefix 1000 90 restart 5

Local Router

Lo1

ip address 172.29.0.68 255.255.255.255

router bgp 65510

network 172.29.0.64 mask 255.255.255.248

neighbor 172.29.0.65 remote-as 65500

neighbor 172.29.0.65 timers 10 30

neighbor 172.29.0.65 send-community both